-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Test failures in 16.9.1 on Linux/rv64 #40152
Labels
riscv64
Issues and PRs related to the riscv64 architecture.
Comments
ArchFeh
added a commit
to ArchFeh/node
that referenced
this issue
Apr 9, 2022
In riscv hardware test-heap-prof.js caused timeout in test because of weak performance. So there is a need to set TIMEOUT_SCALEFACTOR for riscv too. Fixes: nodejs#40152
ArchFeh
added a commit
to ArchFeh/node
that referenced
this issue
Apr 9, 2022
In riscv hardware test-heap-prof.js caused timeout in test because of weak performance. So there is a need to set TIMEOUT_SCALEFACTOR for riscv too. Fixes: nodejs#40152
ArchFeh
added a commit
to ArchFeh/node
that referenced
this issue
Apr 9, 2022
In riscv hardware test-heap-prof.js caused timeout in test. Because of weak performance. So there is a need to set TIMEOUT_SCALEFACTOR for riscv too. Fixes: nodejs#40152
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Version
v16.9.1
Platform
Linux 5.13.14 riscv64
Subsystem
No response
What steps will reproduce the bug?
python tools/test.py --mode=release --flaky-tests=dontcare -J message parallel sequential
How often does it reproduce? Is there a required condition?
Every time so far.
What is the expected behavior?
All tests pass.
What do you see instead?
parallel/test-corepack-yarn-install and sequential/test-cpu-prof-dir-absolute fail, sequential/test-heap-prof times out. Attaching full test output.
nodejs-16.9.1-test.log.gz
Additional information
No response
The text was updated successfully, but these errors were encountered: