benchmark: http simple connect timeout on macOS

[SASUKE40]

• Version: v13.11.0
• Platform: macOS Catalina
• Subsystem: benchmark

What steps will reproduce the bug?

node benchmark/http/simple.js

How often does it reproduce? Is there a required condition?

Always reproduces.

What is the expected behavior?

It should run without timeout error on macOS.

What do you see instead?

Additional information

I found that it works when I change duration from 5 to 10. It could be some problem with frequently port binding.

const bench = common.createBenchmark(main, {
  // Unicode confuses ab on os x.
  type: ['bytes', 'buffer'],
  len: [4, 1024, 102400],
  chunks: [1, 4],
  c: [50, 500],
  chunkedEnc: [1, 0],
  duration: 5 // replace with 10, it works
});

[himself65]

can you enable NODE_DEBUG=net and log the output?

and it seems like the macOS only issue, it's okay on my windows10 and WSL

[SASUKE40]

can you enable NODE_DEBUG=net and log the output?

and it seems like the macOS only issue, it's okay on my windows10 and WSL

NET 98415: SERVER handle? true   connections? 0
NET 98415: emit close
NET 98419: _read
NET 98415: _read
NET 98419: createConnection [
  {
    protocol: 'http:',
    hostname: '127.0.0.1',
    hash: '',
    search: '',
    pathname: '/bytes/4/1/normal/0',
    path: null,
    href: 'http://127.0.0.1:12346/bytes/4/1/normal/0',
    port: 12346,
    host: '127.0.0.1',
    servername: '',
    _agentKey: '127.0.0.1:12346:',
    encoding: null
  },
  [Function: oncreate],
  [Symbol(normalizedArgs)]: true
]
NET 98415: _read
NET 98419: pipe false null
NET 98415: _read
NET 98419: _final: not ended, call shutdown()
NET 98415: _read
NET 98419: _read
NET 98419: _read wait for connection
NET 98415: _read
NET 98419: destroy
NET 98419: close
NET 98415: _read
NET 98419: close handle
NET 98415: _read
NET 98419: afterShutdown destroyed=true ReadableState {
  objectMode: false,
  highWaterMark: 16384,
  buffer: BufferList { head: null, tail: null, length: 0 },
  length: 0,
  pipes: [],
  flowing: true,
  ended: true,
  endEmitted: true,
  reading: false,
  sync: false,
  needReadable: false,
  emittedReadable: false,
  readableListening: false,
  resumeScheduled: false,
  errorEmitted: false,
  emitClose: false,
  autoDestroy: false,
  destroyed: true,
  defaultEncoding: 'utf8',
  awaitDrainWriters: null,
  multiAwaitDrain: false,
  readingMore: false,
  decoder: null,
  encoding: null,
  [Symbol(kPaused)]: false
}
NET 98415: _read
NET 98419: emit close
NET 98415: _read
NET 98419: afterConnect
NET 98415: _read
NET 98419: destroy
NET 98419: close
NET 98419: close handle
NET 98415: _read
events.js:292
      throw er; // Unhandled 'error' event
      ^

Error: connect ETIMEDOUT 127.0.0.1:12346
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)
Emitted 'error' event on ClientRequest instance at:
    at Socket.socketErrorListener (_http_client.js:432:9)
    at Socket.emit (events.js:315:20)
    at emitErrorNT (internal/streams/destroy.js:84:8)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  errno: -60,
  code: 'ETIMEDOUT',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 12346
}
NET 98415: _read
NET 98415: destroy
NET 98415: close
NET 98415: close handle
NET 98415: destroy
NET 98415: close
NET 98415: close handle
NET 98415: destroy
NET 98415: close
NET 98415: close handle
NET 98415: emit close
NET 98415: emit close
NET 98415: emit close
NET 98415: SERVER _emitCloseIfDrained
Error: test-double-http failed with 1.
    at ChildProcess.<anonymous> (/Users/shilinzhu/github/SASUKE40/node/benchmark/_http-benchmarkers.js:238:16)
    at Object.onceWrapper (events.js:422:26)
    at ChildProcess.emit (events.js:315:20)
    at maybeClose (internal/child_process.js:1026:16)
    at Socket.<anonymous> (internal/child_process.js:441:11)
    at Socket.emit (events.js:315:20)
    at Pipe.<anonymous> (net.js:674:12)

[bnoordhuis]

It's almost certainly an issue local to your system, like the firewall rejecting localhost connections or macos's network sandboxing system disallowing outgoing connections.

I can't reproduce it on a macos 10.14 system, in any case.

[VictorNanka]

I got same timeout on my mac.

Version: v13.11.0
Platform: macOS Catalina 10.15.3
Subsystem: benchmark

@SASUKE40