Repository navigation
Assert in uv__io_poll #34633
Description
Activity
Interesting... I can tell from the line number that the kevent() system call (what node/libuv uses to suspend itself and wait for new events) timed out even though we told it to wait indefinitely.
It's basically an impossible condition barring kernel bugs - which is probably what you hit here. Is it possible for you to check
uname -aon the affected VM?@bnoordhuis Hello
The result of
uname -aisDarwin Mac-1596700289969.local 19.6.0 Darwin Kernel Version 19.6.0: Sun Jul 5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64 x86_64Also small correction, actually
/Users/runner/runners/2.172.2/externals/node/bin/node --versionisv6.17.1We have started to experience this issue recently and didn't find any changes from image side that could cause it. Also this Node.js was recently updated 9 months ago that can't be root cause too.
Thanks, but... v6.x has been end-of-life'd for over a year so, if nothing else, you should upgrade to a supported version.
I'll close this but let me know if you still run into this with node v1[024].x.
What steps will reproduce the bug?
Unknown 🤷♂️ , failed
only onceon CI.How often does it reproduce? Is there a required condition?
OnceA few timesWhat is the expected behavior?
Run without crashes
What do you see instead?
Additional information
Sorry that there is so little info here, but it doesn't repro on the same VM with same parameters. It's more like notification that this problem exists so you can review/analyze this part of the code.
Just in case: the script is open source https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/XcodeV5/xcode.ts