Assertion failed: (timeout != -1), function uv__io_poll, file ../deps/uv/src/unix/kqueue.c, line 256.

[jeremymeng]

Version

16

Platform

MacOS 11

Subsystem

No response

What steps will reproduce the bug?

This happens in our azure devops build pipeline automation

https://github.com/Azure/azure-sdk-for-js/pull/25355/checks?check_run_id=12237694551

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

No response

What do you see instead?

Assertion failed: (timeout != -1), function uv__io_poll, file ../deps/uv/src/unix/kqueue.c, line 256.
##[error]Exit code 134 returned from process: file name '/Users/runner/runners/2.218.1/externals/node16/bin/node', arguments '"/Users/runner/work/_tasks/CmdLine_d9bafed4-0b18-4f58-968d-86655b4d2ce9/2.212.0/cmdline.js"'.

Additional information

Seems the same as reported in #34633 and microsoft/azure-pipelines-tasks#13785

[bnoordhuis]

It's different from #34633 because I'm fairly sure the error you're seeing is a bug that was introduced in libuv/libuv@e8effd4 and subsequently fixed (if somewhat by accident) in libuv/libuv@42cc412.

That other issue was about an ancient node release that predates both commits by a wide margin.

The fix hasn't made it into any libuv release yet. A v1.45.0 release is planned (libuv/libuv#3887) but will take some time to make it into v16.x.

Since there isn't anything to do for node except wait, I'll go ahead and close this. Thanks for the report.

[bnoordhuis]

Since there isn't anything to do for node

On second thought, node could disable the uv_loop_configure(UV_METRICS_IDLE_TIME) calls in node.cc and node_worker.cc until libuv is upgraded.

[trevnorris]

@bnoordhuis That will break the event loop utilization API (https://nodejs.org/docs/latest/api/perf_hooks.html#performanceeventlooputilizationutilization1-utilization2). If this is necessary then I'd recommend only disabling it for systems that use kqueue.

[bnoordhuis]

I'm not personally invested in this so I'll just go ahead and close it out.

To summarize: known issue, fix pending libuv upgrade, ETA in the next month or so.