Again, for the millionth time, that is a CI problem, not a build system problem.
How is the build system supposed to know? Does Bazel have a magic Rust parser that can understand comment changes?
-
-
Bazel's dependency graph goes down to the file level. If your test doesn't have transitive edges going to a doc, the test will not rerun if the doc changes. That said, if your compiler changes, expect all tests to rerun.
-
This is my point. File-level dependency tracking is something we already do in Cargo. (Actually, Cargo uses incremental compilation, so it’s *better* than file-level.) It wouldn’t have helped this case, precisely because it’s file-level.
- 8 more replies
New conversation -
-
-
The hash is not the same because doc comments end up in the metadata.
- 14 more replies
New conversation -
-
-
Are you saying that it was the product of a single rustc command that was caused by the comment? The fact that every other step had identical-to-cache input was lost inside one opaque compiler invocation?
-
It was not identical-to-cache. Doc comments change metadata; debug info (file/line) changes.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.