test-net-autoselectfamily.js failed
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Version
v20.4.0
Platform
Darwin MacBook-Pro.local 21.6.0 Darwin Kernel Version 21.6.0: Thu Jun 8 23:57:12 PDT 2023; root:xnu-8020.240.18.701.6~1/RELEASE_X86_64 x86_64
Subsystem
net
What steps will reproduce the bug?
Download the latest node from the offical site. https://nodejs.org/dist/v20.4.0/node-v20.4.0-darwin-x64.tar.gz
roger@MacBook-Pro node-contribute % ~/Downloads/node-v20.4.0-darwin-x64/bin/node ~/Work/node-contribute/test/parallel/test-net-autoselectfamily.js
The test-net-autoselectfamily.js I run is from the latest node source.
roger@MacBook-Pro node-contribute % git log
commit f9737b1b8c96e43cedfff764634524df62cf3109 (HEAD -> origin/main, origin/HEAD)
Author: Node.js GitHub Bot <github-bot@iojs.org>
Date: Fri Jul 14 10:37:47 2023 +0100
How often does it reproduce? Is there a required condition?
Consistently reproducable
What is the expected behavior? Why is that the expected behavior?
no complaint, of course
What do you see instead?
node:assert:125
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
-
actual - expected
[
'2606:4700::6810:85e5:56228',
'104.20.22.46:56228',
- '2606:4700::6810:84e5:56228',
- '104.20.23.46:56228',
- '::1:56228',
- '127.0.0.1:56228'
]
at Socket. (/Users/roger/Work/node-contribute/test/parallel/test-net-autoselectfamily.js:145:18)
at Socket. (/Users/roger/Work/node-contribute/test/common/index.js:466:15)
at Socket.emit (node:events:512:28)
at afterConnect (node:net:1578:10)
at afterConnectMultiple (node:net:1675:3) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: [ '2606:4700::6810:85e5:56228', '104.20.22.46:56228' ],
expected: [
'2606:4700::6810:85e5:56228',
'104.20.22.46:56228',
'2606:4700::6810:84e5:56228',
'104.20.23.46:56228',
'::1:56228',
'127.0.0.1:56228'
],
operator: 'deepStrictEqual'
}
Node.js v20.4.0
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running test/parallel/test-net-autoselectfamily.js with the reported Node.js v20.4.0 binary on the listed Darwin platform, then inspect the assertion at line 145 and the related connection setup. Compare the observed address sequence with the test's expected values and establish a fix or test adjustment that passes consistently without the reported assertion failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- networking, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100