Skip to content

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

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

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

Conversation

@jonaprieto

Copy link
Copy Markdown
Collaborator

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 enhancement New feature or request label Jul 2, 2026
@jonaprieto jonaprieto self-assigned this Jul 2, 2026
@jonaprieto jonaprieto force-pushed the ci/rust-cache-bindings branch from d3fa585 to 260ec35 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 260ec35 to d9c09d1 Compare July 3, 2026 02:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant