-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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 doesn't work in dropbox #138199
Comments
What's going on here is that clearing the cache is a good way to hide bugs involving reading from cache (and updating the compiler effectively does that). Which makes these bugs nastily hard to reproduce — a working set of reproduction steps will need to involve something like "compile this code, make this 1-line change, compile it again, see ICE". |
(Included backtrace in the new issue (#138203). Note that there seems to be a difference between |
That's because there are separate artifacts for build and check. Only one set has been corrupted. Based on the fact that you are running into a lot of crashes on an uncomplicated codebase while trying to do this all in dropbox, I am inclined to blame dropbox. The incremental compilation system relies on hard links and file locking being implemented correctly, and if they are not, the variety of crashes you're getting is what would result. |
Builds generally don't like being run on a cloud file system, no matter which language or cloud file system. |
I did not know that. Well I moved the project out of Dropbox and haven't seen the crash again, so that was probably the issue. |
Maybe it would make sense to document it more clearly that weird filesystems are not supported by incremental compilation. So we have at least something to point to that explains it in more detail |
The problem there would be communicating to the people who actually need to know that weird filesystems may not work, and also defining what weird means. I'm sure people successfully use incr comp on all sorts of filesystems and we just don't hear about it because why would we. |
I'm sorry, I don't have time to create a minimal example for this, but I will keep the following commit unsquashed for a little while anyway:
aetilley/cool_rust@29e7613
Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: