Repository navigation
Conversation
luiyen
approved these changes
Nov 3, 2026
The e2e job was the slowest in CI (about 9 minutes, against 2 for every other job), and a release waits for CI on the tagged commit, so it set the release's time. E2E_PART now runs one of three parts of scripts/e2e.sh, each about a third of the suite in the last run: runs (the fixture suite and the commands that read its job: jobs, traces, the viewer; ~220s), isolation (integrity, egress, secrets; ~90s) and cli (the rest of the CLI; ~220s). The ci.yml job is a matrix over the three, each uploading its own job dirs on a failure. Unset, the script runs all three as before. The macOS jobs stay as they are. Their runners queued for minutes on two of the last 14 CI runs, but building both macOS targets in one job would add about 5 minutes to every release to save that wait only sometimes.
Closed
Merged
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.
The e2e job was CI's slowest at about 9 minutes; every other job takes under 2. A release waits for CI on the tagged commit, so E2E set the release time: v0.3.11 took 9.5 minutes end to end.
scripts/e2e.shnow takesE2E_PART, andci.ymlruns its three parts as a matrix. Times are from the last run's log:runsjobs,traces, the viewerisolationclitrials, datasets, sweeps,exec,analyze/check, start-env/cache, live syncEach part keeps the leaked-container check and uploads its own job dirs (
e2e-jobs-<part>) when it fails. Unset, the script runs all three as before. Sections are only wrapped inif part …; then … fi; their bodies are unchanged.With the split, E2E should take about 4–5 minutes, and a release about 6, limited by the 5-minute release builds.
The macOS jobs are unchanged. Their runners queued on 2 of the last 14 CI runs: v0.3.9 waited up to 34 minutes, and v0.3.12 about 14. Building both macOS targets in one job would add about 5 minutes to every release, to save that wait only some of the time.
Checks
bash -n scripts/e2e.shpasses, and an unknownE2E_PARTexits 2 with a message.E2E (<part>)jobs don't block merging.