-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
OSX: intermittent failure: async-hooks/test-callback-error #15208
Comments
Looks like the macOS machine got re-provisioned but the step about disabling ReportCrash probably didn't happen. See #13527 (comment). @nodejs/build Can someone run those commands? (It needs to be from GUI login unfortunately, so you can't just SSH in.) And also if it's possible to automate those two commands somehow in Ansible or something, that would be great, but I'm not sure how difficult that is given the GUI login requirement. |
Hmmm...actually, this is different it seems. This is a stack crash whereas the previous issue was a timeout, so maybe |
It seems to be crashing after successfully running all three test cases. |
@Trott @mhdawson I was seeing this same behavior on my local OSX tests, and running:
did seem to do the trick; Could you just have Jenkins run that as a pre-test step on OSX (kind of dumb, but works). |
@bcoe Thanks for the information! The commands were run by @rvagg and that seems to have fixed it on CI. So yes, that did the trick after all. Hooray! Rather than running it in Jenkins, I think ansible-minded people on @nodejs/build can hopefully add it to the macOS ansible playbook. Or maybe they'll decide Jenkins is the better place. That's a discussion for https://github.com/nodejs/build. In the meantime, problem solved (for now, at least) so I'm going to close this! |
If ifs a one time thing it should go into ansible. @gdams we need to make sure we include this in the ansible scripts for OSX. |
Failure in run for unrelated change:
https://ci.nodejs.org/job/node-test-commit-osx/12183/nodes=osx1010/console
The text was updated successfully, but these errors were encountered: