investigate flaky test-inspector-cli-heap-profiler on Raspberry Pi

[Trott]

• Test: test-inspector-cli-heap-profiler
• Platform: pi2-docker
• Console Output:

00:44:28 not ok 743 inspector-cli/test-inspector-cli-heap-profiler
00:44:28   ---
00:44:28   duration_ms: 30.804
00:44:37   severity: fail
00:44:37   exitcode: 1
00:44:37   stack: |-
00:44:37     /home/iojs/build/workspace/node-test-binary-arm/test/common/inspector-cli.js:84
00:44:37               reject(new Error([
00:44:37                      ^
00:44:37     
00:44:37     Error: Timeout (10000) while waiting for />\s+$/; found: 
00:44:37     Heap snapshot: 0/0
00:44:37     
00:44:37     Heap snapshot: 0/30077
00:44:37     
00:44:37     Heap snapshot: 10000/30077
00:44:37     Heap snapshot: 20000/30077
00:44:37     
00:44:37     Heap snapshot: 30000/30077
00:44:37     
00:44:37     Heap snapshot: 30076/30077
00:44:37     
00:44:37     Heap snapshot: 30077/30077Heap snaphost prepared.
00:44:37     
00:44:37         at Timeout.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/common/inspector-cli.js:84:18)
00:44:37         at listOnTimeout (node:internal/timers:557:17)
00:44:37         at processTimers (node:internal/timers:500:7)
00:44:37   ...

• Build Links: https://ci.nodejs.org/job/node-test-binary-arm-12+/10636/RUN_SUBSET=3,label=pi2-docker/console

[Trott]

Checking to see if this is just a case of Pi devices needing a longer timeout. (The inspector-cli module is already using common.platformTImeout() to give Pi devices twice as much time but maybe more is needed.)

Can't use the usual CI stress test job for Pi devices, so I've modified the Makefile to run stress tests. And for good measure, running it on everything.

Stress test effectively against master: https://ci.nodejs.org/job/node-test-commit/46418/

Stress test with the timeout doubled: https://ci.nodejs.org/job/node-test-commit/46419/

[Trott]

Checking to see if this is just a case of Pi devices needing a longer timeout. (The inspector-cli module is already using common.platformTImeout() to give Pi devices twice as much time but maybe more is needed.)

Can't use the usual CI stress test job for Pi devices, so I've modified the Makefile to run stress tests. And for good measure, running it on everything.

Stress test effectively against master: https://ci.nodejs.org/job/node-test-commit/46421/

Stress test with the timeout doubled: https://ci.nodejs.org/job/node-test-commit/46420/

[richardlau]

Can't use the usual CI stress test job for Pi devices

I have no idea if it works but there’s
https://ci.nodejs.org/view/Stress/job/node-stress-single-test-pi1-fanned/
(One of several jobs I had no idea existed until I enumerated all of them in nodejs/build#2619.)

[Trott]

Can't use the usual CI stress test job for Pi devices

I have no idea if it works but there’s
https://ci.nodejs.org/view/Stress/job/node-stress-single-test-pi1-fanned/
(One of several jobs I had no idea existed until I enumerated all of them in nodejs/build#2619.)

I assume that one doesn't work because we don't have Pi 1 devices anymore.

[Trott]

Neither stress tests had any relevant failures. ncu-ci walk commit finds only the failure documented here. I'm going to close this because frequency is low enough that we can't replicate it, really. And the Pi 3 devices have been wonky for other reasons lately. We can re-open this if it recurs.

[Trott]

Found another one.

https://ci.nodejs.org/job/node-test-binary-arm-12+/10602/RUN_SUBSET=3,label=pi2-docker/testReport/junit/(root)/test/inspector_cli_test_inspector_cli_heap_profiler/

19:57:06 not ok 744 inspector-cli/test-inspector-cli-heap-profiler
19:57:06   ---
19:57:06   duration_ms: 33.994
19:57:06   severity: fail
19:57:06   exitcode: 1
19:57:06   stack: |-
19:57:06     /home/iojs/build/workspace/node-test-binary-arm/test/common/inspector-cli.js:87
19:57:06               reject(new Error([
19:57:06                      ^
19:57:06     
19:57:06     Error: Timeout (10000) while waiting for />\s+$/; found: 
19:57:06     Heap snapshot: 0/0
19:57:06     
19:57:06     Heap snapshot: 0/30077
19:57:06     
19:57:06     Heap snapshot: 10000/30077
19:57:06     
19:57:06     Heap snapshot: 20000/30077
19:57:06     
19:57:06     Heap snapshot: 30000/30077
19:57:06     
19:57:06     Heap snapshot: 30076/30077
19:57:06     
19:57:06     Heap snapshot: 30077/30077
19:57:06     
19:57:06     Heap snaphost prepared.
19:57:06     
19:57:06         at Timeout.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/common/inspector-cli.js:87:18)
19:57:06         at listOnTimeout (node:internal/timers:557:17)
19:57:06         at processTimers (node:internal/timers:500:7)
19:57:06   ...

[Trott]

I wonder if this has to do with NFS performance.