[INFO] fetching crate thread_aware_macros 0.2.0...
[INFO] checking thread_aware_macros-0.2.0 against master#cf8a95590a1b768b7711f2631d5b5e3ead464de7 for pr-149389
[INFO] extracting crate thread_aware_macros 0.2.0 into /workspace/builds/worker-5-tc1/source
[INFO] started tweaking crates.io crate thread_aware_macros 0.2.0
[INFO] removed 0 missing tests
[INFO] finished tweaking crates.io crate thread_aware_macros 0.2.0
[INFO] tweaked toml for crates.io crate thread_aware_macros 0.2.0 written to /workspace/builds/worker-5-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate thread_aware_macros 0.2.0 on toolchain cf8a95590a1b768b7711f2631d5b5e3ead464de7
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cf8a95590a1b768b7711f2631d5b5e3ead464de7" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate crates.io crate thread_aware_macros 0.2.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" "+cf8a95590a1b768b7711f2631d5b5e3ead464de7" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr] error: checksum for `thread_aware_macros_impl v0.2.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 `thread_aware_macros_impl v0.2.0` is the same as when the lockfile was generated
[INFO] [stderr] 


command failed: exit status: 101

    Updating crates.io index
error: checksum for `thread_aware_macros_impl v0.2.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 `thread_aware_macros_impl v0.2.0` is the same as when the lockfile was generated
