Revert #137: it destabilized the daemon-gates (syncookie-v6 wedged on main) #152
No reviewers
Labels
No labels
bug
deploy
documentation
duplicate
enhancement
good first issue
help wanted
invalid
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
femboy/blackwall!152
Loading…
Reference in a new issue
No description provided.
Delete branch "sp-revert-137"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reverts #150 (the #137 lab-teardown-residue fix). It regressed previously-green gates: on main,
deception-syncookie-v6wedged (~24min on a 6min step) — that gate had passed reliably for many runs before #137. In PR #151,deception-syncookiewedged similarly. Both are daemon-gates that were stable pre-#137.Cause: the #137 change added an unbounded pre-gate
sudo lab downbefore every gate plus areap_orphan_lab_procs()pkill— one of these intermittently hangs / races the daemon-gates' engine, wedging a gate that used to pass.Reverting restores the known-green state (original teardown, no pre-gate sweep, the 4 known-flaky gates quarantined). The #137 root-cause finding (orphans in anonymous namespaces) stands and is documented on the issue — but the fix needs a bounded, non-racy reimplementation (timeout-wrap the sweep; make the orphan
pkillsignature strictly scoped and incapable of matching a live gate's engine) before re-landing. #137 stays open.Restores CI to green; no product code affected (lab-harness + CI only).