-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
parallel/test-dotenv-node-options skipped #50346
Comments
It's not obvious to me either. In https://ci.nodejs.org/job/node-test-commit-linux/nodes=rhel8-x64/54511/consoleFull we see: 19:59:23 ok 927 parallel/test-dotenv-edge-cases # skip 0
19:59:23 ---
19:59:23 duration_ms: 276.99400
19:59:23 ...
19:59:23 ok 928 parallel/test-dotenv-node-options # skip 0
19:59:23 ---
19:59:23 duration_ms: 311.21900
19:59:23 ... Both of which are marked skipped:
Maybe it's a testcase issue, or testrunner bug? node/test/parallel/test-dotenv-node-options.js Lines 7 to 9 in 41a3878
However test/parallel/test-dotenv-edge-cases.js does not contain any skip statements.cc @nodejs/test_runner |
FWIW, I have tried running this testcase manually with a combination of flags from https://nodejs.org/api/permissions.html#process-based-permissions but I have never managed to get it to pass. |
It looks like #48929 may have introduced this behavior in the test runner. |
Does this issue still persist? |
Yes. From today's daily build, https://ci.nodejs.org/job/node-test-commit-linux/55932/nodes=rhel8-x64/testReport/(root)/parallel/test_dotenv_node_options_/ still shows the test as being skipped and https://ci.nodejs.org/job/node-test-commit-linux/55932/nodes=rhel8-x64/consoleFull 08:08:48 ok 928 parallel/test-dotenv-edge-cases # skip 0
08:08:48 ---
08:08:48 duration_ms: 269.52700
08:08:48 ...
08:08:48 ok 929 parallel/test-dotenv-node-options # skip 0
08:08:48 ---
08:08:48 duration_ms: 269.23600
08:08:48 ... |
This also appears to affect |
This is the Python test harness (mis)interpreting the |
Fix the Python test harness so that it no longer treats the `# skipped` part of the summary at the end of the built-in test runner output as marking the test as skipped. PR-URL: #53545 Fixes: #50346 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Chemi Atlow <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
Fix the Python test harness so that it no longer treats the `# skipped` part of the summary at the end of the built-in test runner output as marking the test as skipped. PR-URL: #53545 Fixes: #50346 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Chemi Atlow <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
Fix the Python test harness so that it no longer treats the `# skipped` part of the summary at the end of the built-in test runner output as marking the test as skipped. PR-URL: #53545 Fixes: #50346 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Chemi Atlow <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
Fix the Python test harness so that it no longer treats the `# skipped` part of the summary at the end of the built-in test runner output as marking the test as skipped. PR-URL: #53545 Fixes: #50346 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Chemi Atlow <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
Fix the Python test harness so that it no longer treats the `# skipped` part of the summary at the end of the built-in test runner output as marking the test as skipped. PR-URL: #53545 Fixes: #50346 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Chemi Atlow <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
I noticed that
parallel/test-dotenv-node-options
is skipped in the Linux CI/CD test results on Jenkinseg: https://ci.nodejs.org/job/node-test-commit-linux/nodes=rhel8-x64/lastCompletedBuild/testReport/(root)/parallel/test_dotenv_node_options_/
I also checked
test/parallel/parallel.status
and it doesn't look like this testcase was ever marked as skipped.Does anyone know why this is skipped? Is there an issue with the testcase or the dotenv feature?
Thanks
The text was updated successfully, but these errors were encountered: