Repository navigation
parallel/test-http-multi-line-headers timeout on smartos16 #11019
Description
Activity
As I mentioned in #11026 (comment), I'll take a look at these failures early next week.
Looking at it now.
To paraphrase what I wrote in #11026:
So far, I haven't been able to reproduce the problem described by any of the issues listed above.
In order to be able to get more information and investigate future spurious failures, I submitted a PR that sends
SIGABRTinstead ofSIGTERMto test processes that timeout. This will allow us to take a look at core files generated from these processes with tools such as llnode and mdb_v8, and will potentially help us root cause these issues.In the meantime I'll continue trying to reproduce and investigate those issues, I'll keep you posted.
Again, pasting what I wrote in #11026 to make sure anyone coming here is aware of the current progress on this issue.
#11086 was merged and nodejs/build#613 was created to make tests that time out generate a core file that could be inspected to help root cause these failures.
Thus, I'd suggest that we mark this test (and the other flaky ones mentioned in #11026 (comment)) as flaky on SmartOS.
Then we should make sure that when a build is marked "unstable" on SmartOS, we grab the core files that are generated and upload them somewhere (we can use Joyent's manta for that, as this is part of the resources donated by Joyent to the project) where they won't be cleaned up for further investigation.
How does that sound?
Haven't seen this in several months. Closing, but feel free to comment (or re-open) if it's still A Thing.
Failure when running test for unrelated PR, likely intermittent
https://ci.nodejs.org/job/node-test-commit-smartos/6560/nodes=smartos16-64/console
not ok 829 parallel/test-http-multi-line-headers --- duration_ms: 60.98 severity: fail stack: |- timeout ...