ci: install tempo binary in test workflow#70
Merged
Conversation
commit: |
The tempo binary was missing from CI, causing all native Instance.tempo() tests to timeout (Pool.test.ts, Server.test.ts, tempo.test.ts). Downloads a pinned release (v1.5.0) from GitHub Releases with actions/cache so it's only fetched once per version bump.
25ef9bb to
8d3ac95
Compare
tmm
approved these changes
Mar 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
tempobinary is not installed in CI. The workflow sets up Foundry (anvil) and Docker, but never installstempo. This causes all nativeInstance.tempo()tests to timeout at 10s:Solution
Download a pinned
temporelease binary (v1.5.0) from GitHub Releases, cached withactions/cache@v4keyed on version + OS + arch.x86_64-unknown-linux-gnutarball (~30MB) fromtempoxyz/temporeleasesv1.5.0in two places (cache key + install step)Follows the same pattern used in
tempoxyz/changelogsfor binary caching.