-
Notifications
You must be signed in to change notification settings - Fork 30k
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: skip test-cpu-prof in debug builds with code cache #27308
Conversation
The CPU profiler crashes in debug builds when code cache is enabled. Skip the test temporarily until it's fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m 👍 to fast-tracking if you want
Fixed the linter and the skip message. @addaleax Let's see if this is green in CI first..(it passes for me locally, previously it always crashed) |
CI is green. Please thumb this up if you are +1 to fast tracking (this unbreaks debug builds on master) @nodejs/testing |
Landed in b66f01d |
@@ -3,6 +3,13 @@ | |||
// This tests that --cpu-prof and --cpu-prof-path works. | |||
|
|||
const common = require('../common'); | |||
if (process.features.debug && | |||
process.config.variables.node_code_cache_path === 'yes') { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ATM this is not the best predicate for embedded code-cache...
I've submitted #27311 to fix the value, and this predicate (it could be any non ''
value if combined with the previous manual embedding technique)
The CPU profiler crashes in debug builds when code cache is
enabled. Skip the test temporarily until it's fixed.
Refs: #27307
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes