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
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:
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
Version
v19.0.0-pre, ref-parse HEAD: 87b9a77
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:
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: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:
I assume it's the case for other failing tests.
The text was updated successfully, but these errors were encountered: