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: work around ENOTEMPTY when cleaning tmp dir #30849
Conversation
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
|
It's currently failing like this so that sounds plausible. |
This comment has been hidden.
This comment has been hidden.
|
Still the same error after rebasing on top of master (now that #30785 is merged): |
|
Looking at the full stack trace, I think I see what the problem is. In #30785, I updated the synchronous retry logic where the original rimraf code just retried in a loop. But it's possible that that code is never even reached if errors are encountered in the |
|
Is there a chance we also run into a race condition on Seems like using similar logic for both would be appropriate? |
|
@bnoordhuis if you rebase this now things should, hopefully, be working |
|
Can you also remove the |
Replace the homegrown rimrafsync implementation in test/common with
a call to `fs.rmdirSync(path, { recursive: true })`.
Fixes: nodejs#30620
Fixes: nodejs#30844
|
Thanks, Colin. Updated + rebased: https://ci.nodejs.org/job/node-test-pull-request/27586/ |
|
Are the changes to test/parallel/parallel.status intentional or unrelated? |
Oh, I see, yeah, it's intentional. Ignore my question. |
|
Landed in edf654d |
Replace the homegrown rimrafsync implementation in test/common with
a call to
fs.rmdirSync(path, { recursive: true }).Fixes: #30620
Fixes: #30844
cc @joaocgreis