Investigate flaky test - parallel/test-common-expect-warning

[richardlau]

Test

parallel/test-common-expect-warning

Platform

Linux

Console output

not ok 325 parallel/test-common-expect-warning
  ---
  duration_ms: 0.782
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:1026
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The input did not match the regular expression /Unexpected extra warning received/. Input:
    
    ''
    
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/parallel/test-common-expect-warning.js:41:14)
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/common/index.js:416:15)
        at ChildProcess.emit (node:events:527:28)
        at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '',
      expected: /Unexpected extra warning received/,
      operator: 'match'
    }
    
    Node.js v18.0.0-pre
  ...

Build links

• https://ci.nodejs.org/job/node-test-commit-arm/40770/nodes=ubuntu1804-arm64/testReport/junit/(root)/test/parallel_test_common_expect_warning/
• https://ci.nodejs.org/job/node-test-commit-arm-debug/872/nodes=ubuntu1804-arm64/testReport/junit/(root)/test/parallel_test_common_expect_warning/

Additional information

According to https://github.com/nodejs/reliability/issues?page=2&q=is%3Aissue+is%3Aopen+%22parallel%2Ftest-common-expect-warning%22 this first showed up on 2022-01-04 -- the test was added on 2021-12-30 by 0465373 so this may have been inherently flaky from the start.

[benjamingr]

This can probably be solved by moving the file to mjs, doing toArray instead of .on('data' from the child to avoid truncation?

[lpinca]

No failures in the last 7 days. It seems that #42046 reduced the flakiness.

[lpinca]

No new failures in a long time. I'm closing this.