-
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
investigate flaky test-child-process-fork-exec-path in CI #30620
Labels
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
windows
Issues and PRs related to the Windows platform.
Comments
This one is failing very frequently. Here is a recent example: https://ci.nodejs.org/job/node-test-binary-windows-js-suites/68/RUN_SUBSET=3,nodes=win2012r2-COMPILED_BY-vs2019-x86/testReport/junit/(root)/test/parallel_test_child_process_fork_exec_path/ running on https://ci.nodejs.org/computer/test-rackspace-win2012r2_vs2013-x64-2/ |
richardlau
added
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
windows
Issues and PRs related to the Windows platform.
labels
Dec 8, 2019
bnoordhuis
added a commit
to bnoordhuis/io.js
that referenced
this issue
Dec 12, 2019
Replace the homegrown rimrafsync implementation in test/common with a call to `fs.rmdirSync(path, { recursive: true })`. Fixes: nodejs#30620 Fixes: nodejs#30844
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
windows
Issues and PRs related to the Windows platform.
ref: https://ci.nodejs.org/job/node-test-binary-windows-2/COMPILED_BY=vs2017,RUNNER=win2008r2-vs2017,RUN_SUBSET=1/4420/console
The text was updated successfully, but these errors were encountered: