Rebuild triggered after touching a (git submodule) file under the registry/src directory
#10223
Labels
Comments
|
You can try seeing why Cargo is rebuilding with: and that should print out why the rebuild is happening |
|
|
the following in our - name: Zero mtimes of deps
run: |
set -euxo pipefail
CARGO_DIR="${CARGO_HOME:-$HOME/.cargo}"
for source in "$CARGO_DIR"/registry/cache/*/; do
pushd "$source"
source=$(basename -- "$PWD")
mkdir -p "$CARGO_DIR/registry/src/$source"
for crate in *.crate; do
crate=${crate%.crate}
mkdir "$CARGO_DIR/registry/src/$source/$crate" || continue
tar --strip-components=1 -xzf "$crate.crate" -C "$CARGO_DIR/registry/src/$source/$crate"
echo -n ok > "$CARGO_DIR/registry/src/$source/$crate/.cargo-ok"
done
popd
done
find "$CARGO_DIR/registry/src" -exec touch -cfht 197001010000 {}
``` |
|
Does the rocksdb build script print out a |
|
#11613 has us no longer checking the mtime for "immutable" sources. It looks like that should resolve this, so I'm closing this. If there is a reason to reconsider, let us know! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
rocksdbas a representativehello, world!executablerocksdb = "0.17.0"as a dependency.clangorllvmas per the crate requirementscargo build5.a.
rm -rf ~/.cargo/registry/src5.b. (alternate rebuild trigger)
touch /path/to/registry/src/directory/librocksdb-sys-6.20.3/rocksdbcargo buildand observe the rebuild being triggered.To validate this is unique, I followed the steps with other executables using the
rmoption, without any issues.Possible Solution(s)
touch, issue [WIP] mtime content tracking #8623 could fix itNotes
The re-build appears to be triggered by this line of code
The CI setup is following the advice outlined here
Version
The text was updated successfully, but these errors were encountered: