Santiago Gimeno

@sidorares sure @aselivanov yes, some tests are needed. Let me know if you need help with them

This [commit](https://github.com/nodejs/node-v8/commit/8bb7d253d416bb0fb12cb9b6a040559c5a83d437) fixes the issue for me. Should I open a PR in this repo or somewhere else?

Done. Thanks @targos

@codebytere by looking at the stacktrace I'm not sure it is related to the patch. Regardless, what should I do to reproduce this locally? I can't see any crashes when...

Published as `v1.0.1`

Can we have those jobs added even if we have currently some failing tests?

> Looks like that was introduced by #3803. As far as I can tell, `sched_getcpu()` is glibc-specific I think it was added in FreeBSD 13.1. So this check should be...

Yes, `1.45.0`: https://github.com/libuv/libuv/issues/3887. There's no regular release schedule. Usually we cut a release when we think there's enough new features/fixes. (or in the event of some major regression)

If I'm reading this correctly there are 2 separate issues here. - The crash in some instances. This seems to be directly related to a bug with docker and nothing...

So, I think there's a regression in libuv which might be solved in https://github.com/libuv/libuv/pull/4341. Regardless, just curious why the need to call `child.kill()` in those tests as the child processes...