-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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 sequential/test-benchmark-http times out on AIX #20389
Comments
Running it on the command line, I can see that the next benchmark would be http/create-clientrequest.js, so somehow it would seem that benchmark is getting in an infinite loop or similar state on AIX. At least, that would be my first guess. |
(Also, that benchmark is being called with |
Definition of the error code reported is not meaningful to any source line in the benchmark in question. I would declare it as an infra issue. |
or |
@gireeshpunathil |
ok thanks, I messed up exit code with errno. Unable to reproduce locally, after a 1000 runs! will review the code to see any potential for a hang. |
It's very likely to be the cluster benchmark. Yes, it finishes but the cluster likely doesn't shut down correctly. This would also align with the other recent CI failures around the cluster module (e.g. on OS X where child processes have been getting left behind recently). Chances are we're exposing a recently introduced bug in all this. |
I think this might've been fixed? I'll close it out and we can reopen if it fails again. |
There are timeouts showing in https://ci.nodejs.org/job/node-stress-single-test/1828/nodes=aix61-ppc64/console… not sure how to debug this. :/
Example CI failure
The text was updated successfully, but these errors were encountered: