[INFO] fetching crate rerup 1.0.9... [INFO] checking rerup-1.0.9 against try#5de9e0e6cf775e94e0de2003f35e183f3f77bfe8 for pr-143808 [INFO] extracting crate rerup 1.0.9 into /workspace/builds/worker-4-tc2/source [INFO] started tweaking crates.io crate rerup 1.0.9 [INFO] finished tweaking crates.io crate rerup 1.0.9 [INFO] tweaked toml for crates.io crate rerup 1.0.9 written to /workspace/builds/worker-4-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate rerup 1.0.9 on toolchain 5de9e0e6cf775e94e0de2003f35e183f3f77bfe8 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+5de9e0e6cf775e94e0de2003f35e183f3f77bfe8" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate crates.io crate rerup 1.0.9 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+5de9e0e6cf775e94e0de2003f35e183f3f77bfe8" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] error: checksum for `env v0.0.0` changed between lock files [INFO] [stderr] [INFO] [stderr] this could be indicative of a few possible errors: [INFO] [stderr] [INFO] [stderr] * the lock file is corrupt [INFO] [stderr] * a replacement source in use (e.g., a mirror) returned a different checksum [INFO] [stderr] * the source itself may be corrupt in one way or another [INFO] [stderr] [INFO] [stderr] unable to verify that `env v0.0.0` is the same as when the lockfile was generated [INFO] [stderr] [INFO] checking rerup-1.0.9 against try#5de9e0e6cf775e94e0de2003f35e183f3f77bfe8 for pr-143808 [INFO] extracting crate rerup 1.0.9 into /workspace/builds/worker-4-tc2/source [INFO] started tweaking crates.io crate rerup 1.0.9 [INFO] finished tweaking crates.io crate rerup 1.0.9 [INFO] tweaked toml for crates.io crate rerup 1.0.9 written to /workspace/builds/worker-4-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate rerup 1.0.9 on toolchain 5de9e0e6cf775e94e0de2003f35e183f3f77bfe8 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+5de9e0e6cf775e94e0de2003f35e183f3f77bfe8" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate crates.io crate rerup 1.0.9 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+5de9e0e6cf775e94e0de2003f35e183f3f77bfe8" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] error: checksum for `env v0.0.0` changed between lock files [INFO] [stderr] [INFO] [stderr] this could be indicative of a few possible errors: [INFO] [stderr] [INFO] [stderr] * the lock file is corrupt [INFO] [stderr] * a replacement source in use (e.g., a mirror) returned a different checksum [INFO] [stderr] * the source itself may be corrupt in one way or another [INFO] [stderr] [INFO] [stderr] unable to verify that `env v0.0.0` is the same as when the lockfile was generated [INFO] [stderr] [INFO] checking rerup-1.0.9 against try#5de9e0e6cf775e94e0de2003f35e183f3f77bfe8 for pr-143808 [INFO] extracting crate rerup 1.0.9 into /workspace/builds/worker-4-tc2/source [INFO] started tweaking crates.io crate rerup 1.0.9 [INFO] finished tweaking crates.io crate rerup 1.0.9 [INFO] tweaked toml for crates.io crate rerup 1.0.9 written to /workspace/builds/worker-4-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate rerup 1.0.9 on toolchain 5de9e0e6cf775e94e0de2003f35e183f3f77bfe8 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+5de9e0e6cf775e94e0de2003f35e183f3f77bfe8" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate crates.io crate rerup 1.0.9 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+5de9e0e6cf775e94e0de2003f35e183f3f77bfe8" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] error: checksum for `env v0.0.0` changed between lock files [INFO] [stderr] [INFO] [stderr] this could be indicative of a few possible errors: [INFO] [stderr] [INFO] [stderr] * the lock file is corrupt [INFO] [stderr] * a replacement source in use (e.g., a mirror) returned a different checksum [INFO] [stderr] * the source itself may be corrupt in one way or another [INFO] [stderr] [INFO] [stderr] unable to verify that `env v0.0.0` is the same as when the lockfile was generated [INFO] [stderr] [INFO] checking rerup-1.0.9 against try#5de9e0e6cf775e94e0de2003f35e183f3f77bfe8 for pr-143808 [INFO] extracting crate rerup 1.0.9 into /workspace/builds/worker-4-tc2/source [INFO] started tweaking crates.io crate rerup 1.0.9 [INFO] finished tweaking crates.io crate rerup 1.0.9 [INFO] tweaked toml for crates.io crate rerup 1.0.9 written to /workspace/builds/worker-4-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate rerup 1.0.9 on toolchain 5de9e0e6cf775e94e0de2003f35e183f3f77bfe8 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+5de9e0e6cf775e94e0de2003f35e183f3f77bfe8" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate crates.io crate rerup 1.0.9 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+5de9e0e6cf775e94e0de2003f35e183f3f77bfe8" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] error: checksum for `env v0.0.0` changed between lock files [INFO] [stderr] [INFO] [stderr] this could be indicative of a few possible errors: [INFO] [stderr] [INFO] [stderr] * the lock file is corrupt [INFO] [stderr] * a replacement source in use (e.g., a mirror) returned a different checksum [INFO] [stderr] * the source itself may be corrupt in one way or another [INFO] [stderr] [INFO] [stderr] unable to verify that `env v0.0.0` is the same as when the lockfile was generated [INFO] [stderr] [INFO] checking rerup-1.0.9 against try#5de9e0e6cf775e94e0de2003f35e183f3f77bfe8 for pr-143808 [INFO] extracting crate rerup 1.0.9 into /workspace/builds/worker-4-tc2/source [INFO] started tweaking crates.io crate rerup 1.0.9 [INFO] finished tweaking crates.io crate rerup 1.0.9 [INFO] tweaked toml for crates.io crate rerup 1.0.9 written to /workspace/builds/worker-4-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate rerup 1.0.9 on toolchain 5de9e0e6cf775e94e0de2003f35e183f3f77bfe8 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+5de9e0e6cf775e94e0de2003f35e183f3f77bfe8" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate crates.io crate rerup 1.0.9 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+5de9e0e6cf775e94e0de2003f35e183f3f77bfe8" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] error: checksum for `env v0.0.0` changed between lock files [INFO] [stderr] [INFO] [stderr] this could be indicative of a few possible errors: [INFO] [stderr] [INFO] [stderr] * the lock file is corrupt [INFO] [stderr] * a replacement source in use (e.g., a mirror) returned a different checksum [INFO] [stderr] * the source itself may be corrupt in one way or another [INFO] [stderr] [INFO] [stderr] unable to verify that `env v0.0.0` is the same as when the lockfile was generated [INFO] [stderr] command failed: exit status: 101 error: checksum for `env v0.0.0` changed between lock files this could be indicative of a few possible errors: * the lock file is corrupt * a replacement source in use (e.g., a mirror) returned a different checksum * the source itself may be corrupt in one way or another unable to verify that `env v0.0.0` is the same as when the lockfile was generated