Repository navigation
ci: compile local E2E tests alongside node images - #2405
Open
skylar-simoncelli wants to merge 15 commits into
Open
skylar-simoncelli wants to merge 15 commits into
skylar-simoncelli wants to merge 15 commits into
Conversation
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
skylar-simoncelli
marked this pull request as ready for review
November 9, 2026 21:55
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
chrisferry
previously approved these changes
Nov 9, 2026
Contributor
|
Taking this PR as inspiration, I managed to bump the concurrency of the local-environment tests at a lower-level of granularity - tests now complete in approx. 5 mins: #2408 Suggest we revert the sharding changes here |
Integrate Oscar Bailey’s changes from #2408 through 8b58f32, including the RPC capacity and observation watermark fixes. Replace the two-chain partition with the complete concurrent suite while retaining compilation overlap and Toolkit package selection. Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
Signed-off-by: Skylar Simoncelli <skylar@skylar.email>
This comment has been minimized.
This comment has been minimized.
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.
Overview
Start compiling Local Environment Tests alongside the node-image build, then reuse the compiled binary through the existing shared Earthly cache when the images are ready. Previously this compilation happened after the image dependency completed.
The new
prepare-local-e2ejob builds+local-env-ci-preparewithout an image dependency.+local-env-ciinherits the same target; a cache miss rebuilds normally. The execution layer includes the workflow run ID and attempt so tests actually run. Trusted PRs use the existing self-hosted pool; external forks retain inline compilation on hosted runners.This PR is scoped to local-env compilation scheduling. It contains no bridge test changes, thread-count or faucet changes, RPC configuration changes, Toolkit code or Toolkit workflow changes. Oscar's concurrency work remains in #2408 and Toolkit improvements in #2412. No dependency on either PR is required.
Financial impact
No GHA cash saving or Karpenter cost increase is claimed. No runner infrastructure is added or moved, and existing self-hosted rental cost is unchanged. The benefit is removing local E2E compilation from the post-image-build path. Shared-host queueing and contention can still determine overall PR latency.
🗹 TODO before merging
📌 Submission Checklist
git commit -s) for the DCO🧪 Testing Evidence
Narrowed head
610721154: CI passed on retry attempt 2. Actual logs confirm:cached), and the runtime Cargo check finished in 2.32s. The first preparation compiled in 5m54s (6m37s job).cargo-denyreports neutral.This demonstrates compilation reuse, not a measured overall PR-time reduction. Shared-runner queueing prevented overlap in the first attempt. The 25m55s local-job duration includes the existing serial tests; Oscar's separate concurrency work is not included here.
The first attempt was interrupted when an unrelated branch restarted shared BuildKit using different cache settings. Retrying the interrupted jobs succeeded without changing test code or that branch.
Actionlint, YAML parsing, conflict-marker checks and private-key detection passed locally; no local builds were run. The repository has no pre-commit configuration, so targeted checks used a temporary configuration.
Read-only merge checks show this head combines cleanly with #2408. #2412 has existing conflicts with main in its Toolkit workflow/target; combining this PR adds no new conflict locations. The local-env and Toolkit changes are independently scoped.
Historical evidence from combined head
2ad2d0481: preparation compiled in 6m12s, and the later Cargo check took 2.84s. Local Environment Tests passed all 34 enabled tests plus liveness in a 13m07s job. That head also included Oscar's concurrent tests; its runtime is not a benchmark of this narrowed PR. Earlier 32% and two-chain results likewise do not measure this final scope.Validate actual compilation reuse, test counts, liveness and latest-head required checks. Record queueing and the complete required-check path separately from individual job runtime. No guaranteed overall PR-time reduction is claimed.
🔱 Fork Strategy
Links
docs/ci/pr-critical-path.md