test-dns-promises-lookupService assumes getnameinfo can return named serviceΒ #42164
Copy link
Copy link
Closed
Closed
Copy link
Labels
testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Description
Activity
- addedtestIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
on Mar 1, 2022 - added a commit that references this issue
on Apr 12, 2022 - added a commit that references this issue
on Apr 25, 2022 - added a commit that references this issue
on May 31, 2022 - added a commit that references this issue
on Jun 27, 2022 - added a commit that references this issue
on Jul 11, 2022 - added a commit that references this issue
on Jul 31, 2022 - added a commit that references this issue
on Oct 10, 2022
Metadata
Metadata
Assignees
Labels
testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Version
HEAD
Platform
No response
Subsystem
test
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
On a clean linux chroot without
/etc/services(which is provided by nonessential netbase package, not guaranteed to be installed)What is the expected behavior?
Test should allow
dnsPromises.lookupService('127.0.0.1', 22)to returnservicewith 22 or 'ssh'.What do you see instead?
Additional information
It's the only test assuming getnameinfo will return the service name.