ci: per-PR Alpha vms.ko modpost smoke check (vms-5af) - #848
Open
baron-3dl wants to merge 1 commit into
Open
Conversation
The heavy Alpha gates (alpha-boot-login, alpha-syssvc-suite) are schedule-only, so a shared kernel-core TU that breaks ONLY the Alpha vms.ko cross-build slips past the PR wall and reds the whole Alpha runtime lane until the nightly catches it -- exactly what vms-0cd/#835's tracepoint use did (undefined tracepoint_probe_ register on Alpha; fixed in #847). This is the arch-convergence hole (vms-1d6). New job alpha-vmsko-modpost-smoke runs on every PR that touches the kernel paths (needs.changes.outputs.kernel: src/kernel/**, src/kernel-core/**, src/libvms/ syssvc/**) and on push/schedule: cross-build vms.ko + assert modpost is clean -- NO qemu boot (that stays in the nightly boot-login gate). The kernel build is gha-cached keyed on the build script + patches (NOT the module source), so a src/kernel change is a cache hit and only vms.ko + modpost re-run (a few min). The grep assertion -- not the exit code -- is the gate, because build-vmsko- alpha.sh exits 0 even on a vms.ko FAILED. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Closes the arch-convergence hole (vms-1d6) that let #835/vms-0cd red the whole Alpha runtime lane for a day: its tracepoint use broke ONLY the Alpha
vms.kocross-build (undefinedtracepoint_probe_register/for_each_kernel_tracepointon Alpha), and because the heavy Alpha gates (alpha-boot-login,alpha-syssvc-suite) are schedule-only, it slipped past the PR wall and only surfaced in the nightly (fixed in #847).New job
alpha-vmsko-modpost-smoke— runs on every PR touching the kernel paths (needs.changes.outputs.kernel:src/kernel/**,src/kernel-core/**,src/libvms/syssvc/**) and on push/schedule:vms.koand asserts modpost is clean (RESULT vms.ko: BUILT) — the grep is the gate, becausebuild-vmsko-alpha.shexits 0 even on a vms.ko FAILED.alpha-boot-logingate. This is the cheap half.src/kernelchange is a cache hit and onlyvms.ko+ modpost re-run — a few minutes after the first run.Would have caught #835 at PR time. Verified locally: the assertion PASSes on a real BUILT log and FAILs on a FAILED log; the workflow YAML parses and the job gates on the existing
changes.kerneloutput.🤖 Generated with Claude Code