-
-
Notifications
You must be signed in to change notification settings - Fork 34.1k
test_runner: correctly filter --experimental-config-file #58833
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
Conversation
|
Review requested:
|
This comment was marked as off-topic.
This comment was marked as off-topic.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #58833 +/- ##
==========================================
- Coverage 90.10% 90.08% -0.02%
==========================================
Files 640 640
Lines 188384 188453 +69
Branches 36932 36970 +38
==========================================
+ Hits 169735 169775 +40
- Misses 11356 11395 +39
+ Partials 7293 7283 -10
🚀 New features to boost your workflow:
|
JakobJingleheimer
left a comment
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.
🙌 LGTM
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
There's a related failing CI, I'll investigate ASAP |
|
Ah, yes. Looks like |
|
https://github.com/nodejs/node/blob/main/test%2Fparallel%2Ftest-coverage-with-inspector-disabled.js <-- I keep forgetting this every time: coverage-related tests must be skipped under specific cases 😁 I'll update the test ASAP |
This comment was marked as outdated.
This comment was marked as outdated.
TIL 💡 |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
Landed in 61a0b12 |
PR-URL: #58833 Reviewed-By: Jacob Smith <[email protected]> Reviewed-By: Chemi Atlow <[email protected]>
|
When cherry-picked onto v22.x-staging the test fails: $ out/Release/node --test-reporter=./test/common/test-error-reporter.js --test-reporter-destination=stdout /home/local/rlau/sandbox/github/trees/v22.x/test/parallel/test-runner-cli.js
node:assert:150
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
undefined !== 1
at Object.<anonymous> (/home/local/rlau/sandbox/github/trees/v22.x/test/parallel/test-runner-cli.js:477:12)
at Module._compile (node:internal/modules/cjs/loader:1706:14)
at Object..js (node:internal/modules/cjs/loader:1839:10)
at Module.load (node:internal/modules/cjs/loader:1441:32)
at Function._load (node:internal/modules/cjs/loader:1263:12)
at TracingChannel.traceSync (node:diagnostics_channel:322:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5)
at node:internal/main/run_main_module:36:49 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: undefined,
expected: 1,
operator: 'strictEqual',
diff: 'simple'
}
Node.js v22.19.1-preI suspect it is dependent on other test runner commits that are not on v22.x-staging. |
Fixes #58828