Skip to content

ci(bindings): fix rust cache + retry flaky network tests#546

Open
jonaprieto wants to merge 1 commit into
mainfrom
ci/rust-cache-bindings
Open

ci(bindings): fix rust cache + retry flaky network tests#546
jonaprieto wants to merge 1 commit into
mainfrom
ci/rust-cache-bindings

Conversation

@jonaprieto

@jonaprieto jonaprieto commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Two bindings-CI fixes:

  1. The old actions/cache cached target at the repo root, but the build runs in bindings/ (cd bindings && cargo build), so the real output is bindings/target and the cache never hit (~/.cargo was never cached either). Swatinem/rust-cache@v2 with workspaces: bindings caches the registry/git and bindings/target.
  2. The bindings tests fork live chain RPCs via anvil and intermittently fail on RPC timeouts. The test step now retries up to 3 times, so transient timeouts no longer turn the run red.

@jonaprieto jonaprieto added the ci CI/CD pipeline changes label Jul 2, 2026
@jonaprieto jonaprieto self-assigned this Jul 2, 2026
@jonaprieto jonaprieto changed the title ci(bindings): fix rust cache with Swatinem/rust-cache ci(bindings): fix rust cache + retry flaky network tests Jul 2, 2026
@jonaprieto jonaprieto force-pushed the ci/rust-cache-bindings branch from f1ec9bc to 9ae0302 Compare July 3, 2026 02:34
Replace the hand-rolled actions/cache with Swatinem/rust-cache@v2 at the
default workspace root. This is a Cargo workspace, so the build output
lives in the root `target/`; Swatinem caches that plus `~/.cargo`
(registry + git), keyed on Cargo.lock and the toolchain.

The bindings tests fork live chain RPCs via anvil and flake on transient
RPC timeouts, so the test step retries up to 3 times.
@jonaprieto jonaprieto force-pushed the ci/rust-cache-bindings branch from 9ae0302 to 0c83733 Compare July 3, 2026 02:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci CI/CD pipeline changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant