investigate flaky test_make_callback/test-async-hooks-gcable in CI

[gireeshpunathil]

• Version: master
• Platform: linux-containerized-sharedlibs
• Subsystem: async-hooks

11:13:36 not ok 2592 node-api/test_make_callback/test-async-hooks-gcable
11:13:36   ---
11:13:36   duration_ms: 0.332
11:13:36   severity: crashed
11:13:36   exitcode: -11
11:13:36   stack: |-
11:13:36   ...

ref: https://ci.nodejs.org/job/node-test-commit-linux-containered/nodes=ubuntu1804_sharedlibs_zlib_x64/16212/consoleFull

[gireeshpunathil]

again:

11:26:27 not ok 2592 node-api/test_make_callback/test-async-hooks-gcable
11:26:27   ---
11:26:27   duration_ms: 0.264
11:26:27   severity: crashed
11:26:27   exitcode: -11
11:26:27   stack: |-
11:26:27   ...

ref: https://ci.nodejs.org/job/node-test-commit-linux-containered/nodes=ubuntu1804_sharedlibs_shared_x64/16214/consoleFull

[Trott]

Yeah, this one is out of control today. Always in the containered builds.

[gireeshpunathil]

more instances: https://ci.nodejs.org/job/node-test-commit-linux-containered/nodes=ubuntu1804_sharedlibs_shared_x64/16224/consoleFull

I guess most of the recent CI runs have this affected. Pinning to catch attention.

[gireeshpunathil]

cc @nodejs/v8 @nodejs/async_hooks @nodejs/n-api

[addaleax]

@gireeshpunathil @Trott This is likely impossible to debug without core dumps and without access to the machine in question? I’ll open an access request on nodejs/build.