-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Windows test failures in file.jl: "stat: operation not permitted (EPERM)" #6144
Conversation
@JeffBezanson libuv uses a number of flags to CreateFile to mitigate this. would you mind copying over their work to ios? |
No problem; can you point me in the right direction? |
somewhere in |
Recently looked into the temporary folder that's getting used here, and found |
no, we don't make any effort to delete those, and neither does windows |
Huh? Isn't |
Oh, I guess we do make some effort then. It sounds like we are just inconsistent then. |
@quinnj You had started to look into this. Any progress? Otherwise I'll take a look. |
No, I wasn't sure where to find libuv's CreateFile flags. |
Ok. |
I did the libuv thing, but it didn't actually help. I'm also not sure we have any open references around (which was the original issue). Interestingly this also doesn't fail for me at the REPL. |
Ok, I straced this and it looks like that stat is failing with DELETE_PENDING, which is hardly surprising. |
Anyway, turns out you can't detect DELETE_PENDING from user mode, so unless somebody wants to write a julia_delete kernel module, I say we just merge this pull request and live with it. |
Bummer, thanks for looking into it. Hopefully this won't be a pattern that comes up too frequently in packages or other user code that would lead to Windows-only breakage. |
These are failing with "stat: operation not permitted (EPERM)". There may still be file handles open so the unlinked file and removed directory cannot be stat-ed.
Rebased. |
@Keno ok to merge? Lgtm |
Windows test failures in file.jl: "stat: operation not permitted (EPERM)"
Thanks guys, another Windows test failure down. Underlying problem's still there, but apparently nothing we can do about it and I doubt it's all that consequential. |
This has been seen before by @magistere here. There may still be file handles open so the unlinked file and removed directory cannot be stat-ed. Very similar problem occurs in node: nodejs/node-v0.x-archive#7164. I tried to clean up as much as I could figure out:
but could not get consistent success here. Any suggestions about what might still be open and how to absolutely close it before calling
ispath
on the deleted file and directory? Skipping the test is a workaround, not a real solution.