ci(test): start the Node matrix at dispatch instead of behind the classifier #2073
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2073
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/1119-0227"
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?
Baseline
Classify the changesits in front of all threeTest (Node *)legs and publishes nothing the matrix reads (data_onlyonly standssmoke/dockerdown;liveis now asked by the leg)./actions/tasks, 858Classify the changetasks over 2026-11-17..19: median 7 s, p90 11 s.02:22:05 -> 02:22:11(6 s),Test (Node 18)created02:22:13and finished02:23:14(61 s); run02:22:05 -> 02:23:20= 75 s. Node 18 is the wall clock.02:20:28 -> 02:20:35, legs created02:20:37(9 s).Change
testno longer hasneeds: changes. Legs are created at dispatch.still_open) at step start: same rule (only a positivemerged: true/state: closedstops it), same fail-open direction (no token, timeout, unparseable reply -> run).Coverage unchanged
All three Node legs, the full 344-suite
npm test, the syntax check, the three static scans, both example steps,smoke,dockerandarmare untouched.smoke/dockerstill wait for the classifier, so a data-only diff still stands them down.d1ce3cc67e85c26dc8b0d33c1ce53b43b5d381f2