Repository navigation
test-http2-session-timeout flaky on FreeBSD #15326
Description
Activity
Digging into the test it would appear that this is a timout
server.on('timeout', common.mustNotCall());
Ref #15167 (comment)
- addedfreebsdIssues and PRs related to the FreeBSD platform.Issues and PRs related to the FreeBSD platform.http2Issues and PRs related to the http2 subsystem.Issues and PRs related to the http2 subsystem.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
on Sep 11, 2017 This is not FreeBSD-specific. The test is just straight-up not tolerant of concurrency. Removing the
freebsdlabel.- addedflaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.and removedfreebsdIssues and PRs related to the FreeBSD platform.Issues and PRs related to the FreeBSD platform.
on Sep 11, 2017 Aside: This test uses the
.timeoutproperty of theHttp2Serverclass but that property (and all properties on that class) is undocumented. @nodejs/http2 @nodejs/documentationSimplest solution is to bump up
serverTimeout. Changing it to1200(which is exactly 1/100 of the default value) allows me to run 96 simultaneous copies of the test locally reliably. Previously, I was getting errors sometimes with as few as 8 or 16 concurrent tests, and reliably with 32 concurrent tests.PR coming momentarily.
Fix (or at least mitigation) is in #15328
Sorry, everyone. We're trying to get this nailed down. If someone wants to start a stress test for the latest commit apapirovski@3103f89 that would be appreciated!
Edit: Sorry, this is the PR #15338
If someone wants to start a stress test
I'm on it.
- added a commit that references this issue
on Sep 14, 2017 Still failing on FreeBSD with some frequency.Example: https://ci.nodejs.org/job/node-test-commit-freebsd/11602/nodes=freebsd10-64/console
I'll open a PR to move it to sequential as-is (to get it working right away) and it can be moved back in #15338 whenever that lands.
- added a commit that references this issue
on Sep 16, 2017 - added a commit that references this issue
on Sep 20, 2017 - added 2 commits that reference this issue
on Sep 21, 2017 - added a commit that references this issue
on Jul 27, 2026
This has been showing up a couple times in the v8.5.0-proposal testing
/cc @nodejs/platform-freebsd