-
Notifications
You must be signed in to change notification settings - Fork 892
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
Aggressive remove_dir_all #1015
Conversation
Looks like we might need an aggressive |
I personally forget, but can you clarify how precisely this is more aggressive again? |
It moves the files out of the subdirectory and up next to the directory being deleted, prior to deleting them. This means if the file deletion is delayed due to outstanding locks, then the directories can still be deleted successfully without waiting for other processes to close their file handles. The failure here looks different - like a race condition in one of the self-updater tests possibly? |
Updated to fix the linux build hopefully. |
@bors r+ |
📌 Commit b61370a has been approved by |
Aggressive remove_dir_all Let's see if this helps the flakiness. cc @Diggsey @alexcrichton cc @Aaronepower this PR contains a self-contained remove_dir_all module based on winapi.
💔 Test failed - status-appveyor |
Test failure was network error and i want to deploy this in next release. |
Let's see if this helps the flakiness.
cc @Diggsey @alexcrichton
cc @Aaronepower this PR contains a self-contained remove_dir_all module based on winapi.