flaky test parallel/test-error-reporting on ubuntu1604_sharedlibs_debug_x64

[Trott]

• Version: v10.0.0-pre
• Platform: ubuntu1604_sharedlibs_debug_x64
• Subsystem: test

https://ci.nodejs.org/job/node-test-commit-linux-linked/556/nodes=ubuntu1604_sharedlibs_debug_x64/console

03:21:55 not ok 501 parallel/test-error-reporting # TODO : Fix flaky test
03:21:55   ---
03:21:55   duration_ms: 10.348
03:21:55   severity: flaky
03:21:55   stack: |-
03:21:55     assert.js:42
03:21:55       throw new errors.AssertionError({
03:21:55       ^
03:21:55     
03:21:55     AssertionError [ERR_ASSERTION]: false == true
03:21:55         at /home/iojs/build/workspace/node-test-commit-linux-linked/nodes/ubuntu1604_sharedlibs_debug_x64/test/parallel/test-error-reporting.js:80:10
03:21:55         at /home/iojs/build/workspace/node-test-commit-linux-linked/nodes/ubuntu1604_sharedlibs_debug_x64/test/common/index.js:522:15
03:21:55         at /home/iojs/build/workspace/node-test-commit-linux-linked/nodes/ubuntu1604_sharedlibs_debug_x64/test/parallel/test-error-reporting.js:38:5
03:21:55         at ChildProcess.exithandler (child_process.js:283:5)
03:21:55         at ChildProcess.emit (events.js:159:13)
03:21:55         at maybeClose (internal/child_process.js:943:16)
03:21:55         at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
03:21:55   ...

[Trott]

Possibly related to #17016?

[addaleax]

Yes, it’s exactly that issue… just showing up as a flaky test now because we’ve started including the debug build in CI (the upstream fix & the merge request for V8 6.2 & 6.3 are linked there).

[Ethan-Arrowood]

@addaleax so would the upstream fix & merge request fix this issue? If not is there something i could do to try and remedy it?

[addaleax]

@Ethan-Arrowood Yeah, sorry – this issue is going to be fixed when the patch makes its way into Node, and I’m not sure what else we could do…

[Trott]

(Closed as duplicate of #17016.)