Closed as not planned
Closed as not planned
Description
Problem
Initial presentation of bug
In our CI pipeline, one of our dependencies (specifically rocksdb) will run a rebuild, despite being cached.
Steps
I am using rocksdb
as a representative
- Make minimalist
hello, world!
executable - Add
rocksdb = "0.17.0"
as a dependency. - install
clang
orllvm
as per the crate requirements cargo build
5.a.rm -rf ~/.cargo/registry/src
5.b. (alternate rebuild trigger)touch /path/to/registry/src/directory/librocksdb-sys-6.20.3/rocksdb
- run
cargo build
and observe the rebuild being triggered.
To validate this is unique, I followed the steps with other executables using the rm
option, without any issues.
Possible Solution(s)
- given the bug is reproduced with a
touch
, issue [WIP] mtime+content tracking #8623 could fix it - issue git submodules are not cached #7987 is another issue relating to caching of a submodule
- issue Revert "Disable preserving mtimes on archives" #7935 relates to mtimes, and may offer some insights.
Notes
The re-build appears to be triggered by this line of code
The CI setup is following the advice outlined here
Version
cargo 1.56.0 (4ed5d137b 2021-10-04)
release: 1.56.0
commit-hash: 4ed5d137baff5eccf1bae5a7b2ae4b57efad4a7d
commit-date: 2021-10-04