Skip to content

ci: install tempo binary in test workflow#70

Merged
tmm merged 1 commit intowevm:mainfrom
brendanjryan:ci/install-tempo-binary
Mar 24, 2026
Merged

ci: install tempo binary in test workflow#70
tmm merged 1 commit intowevm:mainfrom
brendanjryan:ci/install-tempo-binary

Conversation

@brendanjryan
Copy link
Contributor

@brendanjryan brendanjryan commented Mar 24, 2026

Problem

The tempo binary is not installed in CI. The workflow sets up Foundry (anvil) and Docker, but never installs tempo. This causes all native Instance.tempo() tests to timeout at 10s:

Solution

Download a pinned tempo release binary (v1.5.0) from GitHub Releases, cached with actions/cache@v4 keyed on version + OS + arch.

  • First run: Downloads the x86_64-unknown-linux-gnu tarball (~30MB) from tempoxyz/tempo releases
  • Subsequent runs: Cache hit, skips download entirely
  • Version bump: Change v1.5.0 in two places (cache key + install step)

Follows the same pattern used in tempoxyz/changelogs for binary caching.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Mar 24, 2026

Open in StackBlitz

npm i https://pkg.pr.new/prool@70

commit: 8d3ac95

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.
@tmm tmm merged commit 0be0728 into wevm:main Mar 24, 2026
5 of 6 checks passed
@brendanjryan brendanjryan deleted the ci/install-tempo-binary branch March 24, 2026 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants