Skip to content
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

OSError: [WinError 17] The system cannot move the file to a different disk drive #388

Closed
alexlib opened this issue Jun 24, 2020 · 10 comments · Fixed by #389
Closed

OSError: [WinError 17] The system cannot move the file to a different disk drive #388

alexlib opened this issue Jun 24, 2020 · 10 comments · Fixed by #389

Comments

@alexlib
Copy link

alexlib commented Jun 24, 2020

File "C:\hostedtoolcache\windows\Python\3.7.7\x64\lib\site-packages\cibuildwheel\windows.py", line 286, in build
   repaired_wheel.replace(options.output_dir / repaired_wheel.name)
 File "C:\hostedtoolcache\windows\Python\3.7.7\x64\lib\pathlib.py", line 1338, in replace
   self._accessor.replace(self, target)
OSError: [WinError 17] The system cannot move the file to a different disk drive: 'C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\cibuildwheeli4q9t16s\\repaired_wheel\\OpenPIV-0.21.9a0-cp36-cp36m-win_amd64.whl' -> 'wheelhouse\\OpenPIV-0.21.9a0-cp36-cp36m-win_amd64.whl'
##[error]Process completed with exit code 1.
@Czaki
Copy link
Contributor

Czaki commented Jun 24, 2020

Which CI?

@joerick So it looks like shutil move should be used again.

@alexlib downgrade to version 1.4.2 until 1.5.1 will be released

@alexlib
Copy link
Author

alexlib commented Jun 24, 2020

@Czaki
Copy link
Contributor

Czaki commented Jun 24, 2020

I wrote about this. I do not understand why current test set doe not catch this.

https://github.com/joerick/cibuildwheel/runs/802745957?check_suite_focus=true

This is result of refactoring from #376

@YannickJadoul
Copy link
Member

Weird indeed, that our tests work with this. I thought we had reasonable coverage :-/

@Czaki
Copy link
Contributor

Czaki commented Jun 24, 2020

It may depend on machine which is selected by CI provider. So it may happen rarely. or even it could be self hosted runner.

@YannickJadoul
Copy link
Member

Alright. Well, at least we noticed when making the change, so we don't need to debug for ages :-)

Does that also mean that just rerunning the job might help @alexlib, for now?

@alexlib
Copy link
Author

alexlib commented Jun 25, 2020

It failed several times on the same line, not once.

@joerick
Copy link
Contributor

joerick commented Jun 25, 2020

Fix released in v1.5.1!

@henryiii
Copy link
Contributor

Was it supposed to have been tagged?

@joerick
Copy link
Contributor

joerick commented Jun 26, 2020

Apologies, forgot to push tags! Should be there now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants