The rust-e2e CircleCI pipeline (.circleci/continue/rust-e2e.yml) runs Go-based E2E tests across 7 job instances but none report test results to CircleCI's Test Insights. This means:
- No per-test timing data for identifying slow tests
- No flake detection for intermittent failures
- No test-level failure visibility — only "job failed"
Approach
Wrap go test invocations with gotestsum --junitfile in the justfiles and add store_test_results / store_artifacts steps to the CI jobs. gotestsum is already available via mise.
Jobs affected
| Job |
Current runner |
rust-e2e-sysgo-tests (4 matrix instances) |
bare go test |
rust-restart-sysgo-tests |
bare go test |
op-reth-e2e-sysgo-tests |
bare go test |
kona-proof-action-tests (4 shards) |
already uses gotestsum but never uploads results |
Acceptance criteria
- All
go test invocations in rust-e2e.yml produce JUnit XML via gotestsum
- All test jobs call
store_test_results to upload results to CircleCI
- Test logs stored as artifacts via
store_artifacts
- No change to test behavior, timeouts, or parallelism
- CI pipeline passes
The rust-e2e CircleCI pipeline (
.circleci/continue/rust-e2e.yml) runs Go-based E2E tests across 7 job instances but none report test results to CircleCI's Test Insights. This means:Approach
Wrap
go testinvocations withgotestsum --junitfilein the justfiles and addstore_test_results/store_artifactssteps to the CI jobs. gotestsum is already available via mise.Jobs affected
rust-e2e-sysgo-tests(4 matrix instances)go testrust-restart-sysgo-testsgo testop-reth-e2e-sysgo-testsgo testkona-proof-action-tests(4 shards)gotestsumbut never uploads resultsAcceptance criteria
go testinvocations in rust-e2e.yml produce JUnit XML via gotestsumstore_test_resultsto upload results to CircleCIstore_artifacts