-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate flaky tests: cpu profiling #20
Comments
i will look it |
|
Also: the tests don't fail in qemu. |
What is your cpu where you get build log? |
i run test on sifive unmatched. |
rv-osuosl-01 is an Hifive Unmatched (SiFive Freedom U740). |
System info:
|
The version of node that fails there is the debianized one... which may explain the difference. The main differences are:
Do you think one of those differences can explain the failures ? |
Note that many failures in those logs are related to some missing extra tools (eslint, npm, ...) so they are not riscv64-related. |
yes , we can only foucs on sequential. |
Test
All sequential profiling tests
Platform
linux/debian bookworm/experimental nodejs 18.6.0
Console output
Currently i can only get the build log with test log (search for "not ok"):
https://buildd.debian.org/status/fetch.php?pkg=nodejs&arch=riscv64&ver=18.6.0%2Bdfsg-2&stamp=1658033553&raw=0
Build links
https://packages.debian.org/source/experimental/nodejs
Additional information
All failing tests:
test-diagnostic-dir-cpu-prof
test-cpu-prof-worker-argv
test-cpu-prof-exit
test-cpu-prof-kill
test-diagnostic-dir-cpu-prof
test-cpu-prof-dir-relative
test-worker-prof
also possibly unrelated:
test-debugger-preserve-breaks
The text was updated successfully, but these errors were encountered: