-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Incremental compilation + case insensitive filesystems == sadness #47222
Comments
Note that this was discovered as part of #47141 in these failing logs. Notably the generated bindings in style for Gecko contains a |
(also the reason for this is that we're putting module names in filenames on the filesystem, and that's how the conflict is arising -- the two module object files get canonicalized into the same file) |
Would this be fixed by switching to using hashes as the filenames as proposed in #47186? |
@retep998 Yes, the same fix should apply. |
…hton Shorten names of some compiler generated artifacts. This PR makes the compiler mangle codegen unit names by default. The name of every codegen unit name will now be a random string of 16 characters. It also makes the file extensions of some intermediate compiler products shorter. Hopefully, these changes will reduce the pressure on tools with path length restrictions like buildbot. The change should also solve problems with case-insensitive file system. cc #47186 and #47222 r? @alexcrichton
This should be fixed by #47269 (which is in the latest nightly already). @alexcrichton, was that a regular NTFS file system you were testing this on? In that case it should be easy to write a regression test (that actually triggers). |
I don't think this is a regression, btw. The underlying logic has been there from pretty much the beginning. |
The regression was when incremental compilation was changed to be enabled by default. |
@michaelwoerister this is indeed fixed, thanks! |
I'll do a backport then. |
Given this code
when compiled on (for example) Windows:
I'll be fixing the ICE as part of #47141 as it's preventing it from landing (the ICE isn't really the issue here anyway, it's the "failed to remove" business). This is also a serious problem for linking artifacts!
cc @michaelwoerister
The text was updated successfully, but these errors were encountered: