-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flaky test-http2-too-many-streams #18657
Comments
I don't get these failures with no stack trace or signal code... No clue where to start. 😕 |
Yeah, they are pretty bad and happening often at the moment 😞. |
@nodejs/build could someone look into these failures without strack traces or signal codes? I feel like these might be more CI or test runner related rather than failures of node or the test itself. |
Are these failing on a specific platform? I'll investigate further. Triggering these reliably can be difficult. |
The ones with no stack trace or signal code have all been on debian8 and ubuntu (I believe 1404 and maybe 1204). |
And I strongly suspect this isn't http2 related. There have been many different tests that have failed this way, across the above mentioned systems. Everything from debug to zlib. |
Happened again today https://ci.nodejs.org/job/node-test-commit-linux/17083/nodes=debian8-x86/console |
I am closing the reports without stack traces. I have the feeling this got resolved. If they come back, we can check again what to do. |
https://ci.nodejs.org/job/node-test-commit-plinux/15046/nodes=ppcbe-ubuntu1404/console
Ping @nodejs/http @nodejs/http2
The text was updated successfully, but these errors were encountered: