-
-
Notifications
You must be signed in to change notification settings - Fork 11k
Build fails for unlinkable_fobjects across windows drive boundaries #16107
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
Comments
Good to have this issue so that error, if it ever comes back to haunt us, is searchable. #16101 is meant to solves this, please reopen if needed. |
As it read it, that PR avoids the broken case, rather than actually fixing |
OK, reopening |
Pretty sure it is this: https://bugs.python.org/issue7195 Perhaps there's a way to switch It may also mean that |
Yeah, I think the fix here would be to work with absolute paths if possible, or emit a better error message if not. |
Here's the documentation I was talking about: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops#avoid-hard-coded-references
Anyway, that's slightly off-topic for this specific issue, but worth keeping in mind long-term. |
One problem with absolute paths may be feeding them to a migw-based compiler, so tests to prove this works will be needed |
Duplicate of #12530 |
Found from a CI run:
The text was updated successfully, but these errors were encountered: