Investigate flaky test-http-server-close-idle

[F3n67u]

Test

test-http-server-close-idle

Platform

Randomly, is not consistent failed at some specific platforms

Console output

not ok 1208 parallel/test-http-server-close-idle
  ---
  duration_ms: 0.60
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:123
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    1 !== 2
    
        at Socket.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-http-server-close-idle.js:48:14)
        at Socket.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/common/index.js:438:15)
        at Socket.emit (node:events:537:28)
        at addChunk (node:internal/streams/readable:324:12)
        at readableAddChunk (node:internal/streams/readable:297:9)
        at Readable.push (node:internal/streams/readable:234:10)
        at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: 1,
      expected: 2,
      operator: 'strictEqual'
    }
    
    Node.js v19.0.0-pre
  ...

Build links

nodejs/reliability#303

Failed PR

2 (nodejs/node#43431, nodejs/node#43391)

Appeared

test-ibm-rhel8-s390x-4, test-rackspace-debian10-x64-1

First CI

https://ci.nodejs.org/job/node-test-pull-request/44560/

Last CI

https://ci.nodejs.org/job/node-test-pull-request/44575/

Example

https://ci.nodejs.org/job/node-test-commit-linuxone/nodes=rhel8-s390x/32480/console

Additional information

Introduced by #42812 on 2022-05-03

The first flaky date is 2022-05-12 nodejs/reliability#273

Query all flaky dates: https://github.com/nodejs/reliability/issues?q=is%3Aissue+is%3Aopen+test-http-server-close-idle

cc @ShogunPanda(Test author)

[F3n67u]

Would fixed by #43216.

[bnoordhuis]

Should be fixed by f8f2772 then.