-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Build is always executed if mtimes are missing #4425
Comments
Hm I'm not actually sure how an mtime can be missing... Did the archive include the |
Hm, that's super weird. I've tried to reproduce it now, and I can't =/ I would say it was a hallucination, if not for the fact that I happen to have one of terminal tabs with experiments laying around, which clearly shows rebuild happening: https://gist.github.com/matklad/0fe6554ecf473b3af9e511e197921614
Yeah, but I think I've tried removing the target directory, and rebuilds still happened, but given that I can't reproduce even the original issue, I am not sure in anything now... |
For the context, the upstream issue is intellij-rust/intellij-rust#1644, which also looks rather mysterious... |
Triage: This issue is quite old, and seemingly hard to reproduce. There's a lot of discussion (some even recent!) in #6529 about moving away from mtimes and to try things like checking hashes. Given this issue here doesn't seem particularly actionable, it probably makes the most sense to just close it. |
Yea, without a clear reproduction this probably isn't actionable. |
Today a user handled me a
rar
archive (from a windows machine) with a Cargo package. When I extracted it on my linux machine, I've noticed thatcargo build
always rebuilds the project, instead of doing zero builds. Looks like the problem is that extracted files missmtime
s, so we always rebulid in here:cargo/src/cargo/ops/cargo_rustc/fingerprint.rs
Lines 250 to 252 in f46d485
Seems like a niche use case, and I am not sure how to fix it properly (touching files seems inappropriate?), but lets log the issue anyways!
The text was updated successfully, but these errors were encountered: