Skip to content
This repository has been archived by the owner on Aug 20, 2021. It is now read-only.

TempDir affected by remove_dir_all unreliability on windows #15

Closed
brson opened this issue Aug 19, 2016 · 7 comments · Fixed by #17
Closed

TempDir affected by remove_dir_all unreliability on windows #15

brson opened this issue Aug 19, 2016 · 7 comments · Fixed by #17

Comments

@brson
Copy link
Contributor

brson commented Aug 19, 2016

I have test cases where TempDir fails to remove the directory mysteriously and irregularly.

cc rust-lang/rust#29497

@brson
Copy link
Contributor Author

brson commented Aug 22, 2016

To fix this I'd suggest extracting the robust remove_dir_all impl from this unmerged PR, along with its test cases, and publishing it to crates.io, then updating TempDir to use that.

@alexcrichton does that sound reasonable to you?

@alexcrichton
Copy link
Contributor

Sounds reasonable to me!

@XAMPPRocky
Copy link
Contributor

I'd like to take this one on if that's alright?

@brson
Copy link
Contributor Author

brson commented Sep 14, 2016

@Aaronepower Yes!

@brson
Copy link
Contributor Author

brson commented Mar 14, 2017

There's an open but unfinished PR for this. What I'd like to happen yet:

  • Move the code into a remove_dir_all_crate
  • Write tests that capture that it works on windows in tricky cases cribbed from this issue.
  • Use winapi instead of duplicating windows definitions
  • Fix tempdir

@XAMPPRocky
Copy link
Contributor

Yeah sorry, I had a winapi implementation however it was wrong, it failed the tests. And then I moved my main development over to macOS so it fell by the wayside. I plan to see if I can finish this over the weekend.

@brson
Copy link
Contributor Author

brson commented Mar 15, 2017

Thanks @Aaronepower ! 😍

@brson brson closed this as completed in #17 May 4, 2017
opilar pushed a commit to opilar/tempdir that referenced this issue Sep 22, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants