-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
test/sequential/test-heapdump.js lines 27 through 39 is bound to fail #41643
Labels
test
Issues and PRs related to the tests.
Comments
I had a same error with current master branch by root in |
RaisinTen
added a commit
to RaisinTen/node
that referenced
this issue
Jan 30, 2022
The test was failing when it was being run with superuser privileges, so this changes the test from attempting to write to a read-only file to attempting to write to a file with the same name as that of an existing directory, as that is a more reliable way of making v8.writeHeapSnapshot() throw even when run with sudo. Fixes: nodejs#41643 Signed-off-by: Darshan Sen <raisinten@gmail.com>
PR: #41772 |
nodejs-github-bot
pushed a commit
that referenced
this issue
Mar 14, 2022
The test was failing when it was being run with superuser privileges, so this changes the test from attempting to write to a read-only file to attempting to write to a file with the same name as that of an existing directory, as that is a more reliable way of making v8.writeHeapSnapshot() throw even when run with sudo. Fixes: #41643 Signed-off-by: Darshan Sen <raisinten@gmail.com> PR-URL: #41772 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
xtx1130
pushed a commit
to xtx1130/node
that referenced
this issue
Apr 25, 2022
The test was failing when it was being run with superuser privileges, so this changes the test from attempting to write to a read-only file to attempting to write to a file with the same name as that of an existing directory, as that is a more reliable way of making v8.writeHeapSnapshot() throw even when run with sudo. Fixes: nodejs#41643 Signed-off-by: Darshan Sen <raisinten@gmail.com> PR-URL: nodejs#41772 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v18.0.0-pre
Platform
No response
Subsystem
No response
What steps will reproduce the bug?
Run tests as root
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
No response
What do you see instead?
Additional information
This test is introduced in the commit 74b9baa
I think the test didn't work because root ignored file permissions
The text was updated successfully, but these errors were encountered: