Investigate flaky test test-http2-pipe-named-pipe on osx-arm

[targos]

It's been happening regularly for some time.

• Test: test-http2-pipe-named-pipe
• Platform: macOS arm64
• Console Output:

node:assert:123
  throw new AssertionError(obj);
  ^

AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

139837 !== 139244

    at WriteStream.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx-arm/nodes/osx11/test/parallel/test-http2-pipe-named-pipe.js:26:12)
    at WriteStream.emit (node:events:402:35)
    at finish (node:internal/streams/writable:751:10)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: 139837,
  expected: 139244,
  operator: 'strictEqual'
}

Node.js v17.0.0-pre

• Build Links: https://ci.nodejs.org/job/node-test-commit-osx-arm/2975/testReport/

[mhdawson]

Seen today: https://ci.nodejs.org/job/node-test-commit-osx-arm/nodes=osx11/3178/

[mhdawson]

Seen again today: https://ci.nodejs.org/job/node-test-commit-osx-arm/nodes=osx11/3294/testReport/(root)/test/parallel_test_http2_pipe_named_pipe/

[targos]

I tried to investigate on my mac (the test fails 30-50% of the runs), but I haven't found anything interesting. I suspect it's a bug in Node.js (not in the test), but I may be wrong.

[Trott]

I tried to investigate on my mac (the test fails 30-50% of the runs), but I haven't found anything interesting. I suspect it's a bug in Node.js (not in the test), but I may be wrong.

This may be asking a lot but if you go to the commit where the test was first added, is it flaky there? If not, perhaps a (no doubt time-consuming) bisect might find something interesting?

[targos]

I tried to investigate on my mac (the test fails 30-50% of the runs), but I haven't found anything interesting. I suspect it's a bug in Node.js (not in the test), but I may be wrong.

This may be asking a lot but if you go to the commit where the test was first added, is it flaky there? If not, perhaps a (no doubt time-consuming) bisect might find something interesting?

I'm afraid that's not possible because the test was added in 2018 and M1 mac support was added last year. IIRC, I've always seen it fail since I bought the laptop in January.