server-immutable-json fails under load: a 6-second readiness wait and no diagnosis #1242
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1242
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
What happens
test/server-immutable-json.test.jsfails intermittently on a loaded machine:It passes when run alone (21 checks). The suite is not flaky in what it asserts — it is flaky in how long
it is willing to wait:
The child it starts is
server/index.js, which loads and serialises a 4.4 MB catalogue before it listens.Six seconds is enough for that on an idle machine and not enough when the test runner is executing other
suites. The failure also reports nothing about why: the child's stderr is discarded, so a genuine startup
failure and a slow startup look identical.
Why it matters
A red suite is what tells everyone the last change broke something. A test that goes red under load
trains people to re-run until green, and the next real failure gets re-run too. It also costs the
automation: the loop this repo is developed under treats a red suite as a stop signal.
Expected
fails with a message naming the deadline.
Scope
The readiness wait in one test file. Nothing about the endpoints or their caching changes.