ci: unbreak the soak, lint workflow files, fingerprint the runner - #67
Merged
Conversation
…rting The comment added in #63 contains a literal empty `${{ }}`. Actions expands expressions in `run:` before any shell sees them, so the `#` protects nothing and the file has been unparseable since f6218b4 — zero-job runs against pushes, nothing on any PR's checks, so #64/#65/#66 all looked green.
A workflow file with a bad expression fails invisibly: GitHub records a zero-job run against a push and shows nothing on any PR. actionlint catches it. Verified to exit 1 on the pre-fix file and 0 on the fixed one. shellcheck/pyflakes integration off on purpose — this checks that the workflow files are valid, and a noisy required check gets removed.
"The runner image" has been carrying the explanation for 2 hits on CI versus 0-for-1190 locally, unmeasured. Measured, five differences survive (CPU, core count, mandatory ASLR, HVCI, Defender) and two expected ones do not — both hosts are build 261xx and both use the client scheduler quantum. Diagnostic only: every probe is optional and the step always exits 0.
deadpoets
force-pushed
the
ci/unbreak-soak-and-lint-workflows
branch
from
August 19, 2026 03:13
0466731 to
ca25dbc
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
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.
The soak has not run since #63
The comment I added in #63 contains a literal empty
${{ }}. Actions expandsexpressions in
run:before any shell sees them, so the#protects nothing —the file has been unparseable ever since.
It fails invisibly: a zero-job run against a push, never against the PR. #64,
#65 and #66 each reported 22/22 green while the soak was dead.
Commits
8b18b5a— drop the delimiter. Verified: dispatched run32210902399
completed successfully, 20 iterations.
390695d—actionlintin thelintjob, pinned to v1.7.12. Verified toexit 1 on the pre-fix file and 0 on the fixed one.
ca25dbc— fingerprint the runner on every soak run.Fingerprint, first result
windows-latestTwo differences I expected turned out not to exist: both hosts are build 261xx,
and both run the client quantum. Worth having measured rather than assumed.
Separately:
GOMAXPROCS=4does not emulate a 4-CPU machine. It caps Go's Pswhile the OS still spreads sysmon, GC workers and the race detector's threads
across all cores — so the ~1190 local samples were never the runner's contention
profile.