Repository navigation
ci: shorten the PR critical path - #786
Merged
Merged
Conversation
- Move the Linux atomics into their own job. The Windows shards need no eBPF object, so they no longer wait ~37s on ebpf-build, and the Atomic (windows) roll-up now covers only the Windows shards. - Split the Windows atomics across three runners instead of two. - Give each ebpf-load leg its own cache. With one shared key the quicker 5.10 leg saved first, so the runner leg's debug build for the live eBPF tests was never cached and spent ~83s compiling before 49s of tests.
Karib0u
force-pushed
the
ci/pr-critical-path
branch
from
October 15, 2026 17:27
2b86e7c to
2e2a4b7
Compare
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.
Stacked on #785 (same file). Merge #785 first; this PR then retargets to main.
Changes
Atomic (linux), same required-check name). The Windows shards need no eBPF object, so they stop waiting about 37s onLinux eBPF Build. TheAtomic (windows)roll-up now covers only the Windows shards, so a Linux failure no longer turns it red too.ebpf-load. Both legs shared one key. The 5.10 leg finishes first and saves a cache without the debug build, so the runner leg's save is skipped andRun live eBPF tests on runner kernelrecompiles every dependency: 83s of compile for 49s of tests on run 38743554001.Expected
On top of #785: the Windows atomic legs start right away and run about 55s shorter, and
Linux eBPF Load (runner)drops by about 80s once main has saved its per-kernel cache. These are estimates from one run's logs and need a warm main run to confirm.zizmor --offlineis clean.