Error running tests on HEAD

Xstoudi commented 2 years ago

Version

v19.0.0-pre, ref-parse HEAD: 87b9a77290cd8727936ef15ea7f460519f8d91f5

Platform

Linux xavier-laptop 5.15.0-48-generic #54-Ubuntu SMP Fri Aug 26 13:26:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

tests

What steps will reproduce the bug?

I simply forked node, cloned it and then followed the BUILDING.md, respectively:

$ sudo apt-get install python3 g++ make python3-pip
$ ./configure
$ make -j4
drink coffee
$ make test-only

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

Always

What is the expected behavior?

All tests should be successfull

What do you see instead?

Some annoying failed tests, logs can be seen here: https://pastebin.com/101XRfEZ

Additional information

My /etc/hosts contains a line for localhost:

127.0.0.1   localhost

I tought that the ENOTFOUND was caused by network condition for some reason, but the failed tests are persisting through company network, home network and mobile network, so...

The error is not related to batch-execution of tests as if I run it directly with the command, it fails anyway:

out/Release/node /data/xavier/contribs/node/test/parallel/test-net-socket-connect-without-cb.js

I assume it's the case for other failing tests.

targos commented 2 years ago

The crypto-related issues should be fixed by https://github.com/nodejs/node/pull/44498.

I don't know about getaddrinfo ENOTFOUND localhost

B0ER commented 1 year ago

Same for me, I always get the error when run tests Logs: https://pastebin.com/bPJ3NYqD Head: 48345d Versions: node - v21.0.0-pre python - 3.10.6 OS - Ubuntu 22.04.2 LTS

Used make + ninja for build

tests don't pass: test/parallel/test-net-socket-connect-without-cb.js test/parallel/test-tcp-wrap-listen.js

nodejs / node