CI's Node 22 job fails intermittently on state-payload-shape, and the failure says nothing #1415

Closed
opened 2026-11-11 02:58:16 +00:00 by jaylouisw · 0 comments
Owner

CI's Test (Node 22) job went red on ebc81a9e (the #1412 merge) and again on the #1414 pull request. Node 18 and Node 20 were green on both, and the same job was green on 37dd4de9, so it is not a code change.

The failing suite is test/state-payload-shape.test.js, and this is the whole of what the run said:

Error: no matching frame within 8000ms
    at Timeout._onTimeout (test/state-payload-shape.test.js:149:60)

Reproduced locally under Node 22.14: one full run failed that suite (0 passed, 1 failed, no summary line), and the next two runs of the same suite on the same build passed 21/21. So it is a flake - but the message is useless for proving that or for finding the cause, because it names neither the frames the client received nor anything the server logged.

What should be true

  1. a wait that expires says what it saw: the frames received, by type;
  2. it says what the server was doing: the tail of the child process's own log;
  3. a cold socket that missed the first frame and a server that never answers are told apart by retrying once on a fresh socket;
  4. a retry that was needed is printed, not swallowed - otherwise the flake is invisible the moment it stops failing the build.
CI's `Test (Node 22)` job went red on `ebc81a9e` (the #1412 merge) and again on the #1414 pull request. Node 18 and Node 20 were green on both, and the same job was green on `37dd4de9`, so it is not a code change. The failing suite is `test/state-payload-shape.test.js`, and this is the whole of what the run said: ``` Error: no matching frame within 8000ms at Timeout._onTimeout (test/state-payload-shape.test.js:149:60) ``` Reproduced locally under Node 22.14: one full run failed that suite (0 passed, 1 failed, no summary line), and the next two runs of the same suite on the same build passed 21/21. So it is a flake - but the message is useless for proving that or for finding the cause, because it names neither the frames the client received nor anything the server logged. ### What should be true 1. a wait that expires says what it saw: the frames received, by type; 2. it says what the server was doing: the tail of the child process's own log; 3. a cold socket that missed the first frame and a server that never answers are told apart by retrying once on a fresh socket; 4. a retry that was needed is printed, not swallowed - otherwise the flake is invisible the moment it stops failing the build.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge#1415
No description provided.