You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Benchmark CI run error: benchmark/_test-double-benchmarker #34061
/Users/ricky/projj/github.com/rickyes/node/benchmark/_test-double-benchmarker.js:40
client.on('error', (e) => { throw e; });
^
Error: connect EADDRNOTAVAIL 127.0.0.1:12346 - Local (0.0.0.0:0)
at internalConnect (net.js:905:16)
at defaultTriggerAsyncIdScope (internal/async_hooks.js:416:12)
at net.js:997:9
at processTicksAndRejections (internal/process/task_queues.js:75:11) {
errno: -49,
code: 'EADDRNOTAVAIL',
syscall: 'connect',
address: '127.0.0.1',
port: 12346
}
Error: test-double-http2 failed with 1.
at ChildProcess.<anonymous> (/Users/ricky/projj/github.com/rickyes/node/benchmark/_http-benchmarkers.js:238:16)
at Object.onceWrapper (events.js:421:26)
at ChildProcess.emit (events.js:314:20)
at maybeClose (internal/child_process.js:1051:16)
at Socket.<anonymous> (internal/child_process.js:442:11)
at Socket.emit (events.js:314:20)
at Pipe.<anonymous> (net.js:656:12)
Is something else running on port 12346 on your machine? If so, you can tell it to use a different port with the NODE_COMMON_PORT environment variable:
Is something else running on port 12346 on your machine? If so, you can tell it to use a different port with the NODE_COMMON_PORT environment variable:
If benchmarking is being throttled by the OS, I'm not sure I have a great suggestion, but maybe someone on @nodejs/benchmarking or @mscdex might have an idea.
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Activity
[-]Benchmark CI run error[/-][+]Benchmark CI run error: benchmark/_test-double-benchmarker[/+]rickyes commentedon Jul 24, 2020
@jasnell @Trott I can't find a way to fix it. Any good suggestions?
Trott commentedon Jul 24, 2020
Trott commentedon Jul 24, 2020
Oops, I made a small-but-important error. In tests, it's
NODE_COMMON_PORTbut apparently in benchmarks, it's justPORT:Note, that I haven't tested this but determined it from reading the code. Sorry if I'm wrong again!
rickyes commentedon Jul 25, 2020
It may not be port usage, I don't have any other programs using port 12346 on my machine, it could be a connection overload error.
rickyes commentedon Jul 30, 2020
It doesn't always happen, but the odds are good that it will.
rickyes commentedon Aug 2, 2020
@addaleax @BridgeAR Any good direction, maybe because the number of threads exceeds the number of connections?
Trott commentedon Aug 7, 2020
If benchmarking is being throttled by the OS, I'm not sure I have a great suggestion, but maybe someone on @nodejs/benchmarking or @mscdex might have an idea.
rickyes commentedon Aug 9, 2020
ping again @mscdex @nodejs/benchmarking
github-actions commentedon Jun 27, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jul 28, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.