[INFO] fetching crate flowtigs 1.1.0...
[INFO] checking flowtigs-1.1.0 against master#779e19d8baa3e3625bd4fc5c85cbb2ad47b43155 for pr-147589-1
[INFO] extracting crate flowtigs 1.1.0 into /workspace/builds/worker-4-tc1/source
[INFO] started tweaking crates.io crate flowtigs 1.1.0
[INFO] finished tweaking crates.io crate flowtigs 1.1.0
[INFO] tweaked toml for crates.io crate flowtigs 1.1.0 written to /workspace/builds/worker-4-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate flowtigs 1.1.0 on toolchain 779e19d8baa3e3625bd4fc5c85cbb2ad47b43155
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+779e19d8baa3e3625bd4fc5c85cbb2ad47b43155" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate crates.io crate flowtigs 1.1.0 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" "+779e19d8baa3e3625bd4fc5c85cbb2ad47b43155" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[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

    Updating crates.io index
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