[INFO] crate pide-rs 0.2.2 is already in cache
[INFO] extracting crate pide-rs 0.2.2 into work/ex/beta-1.38-1/sources/1.37.0/reg/pide-rs/0.2.2
[INFO] extracting crate pide-rs 0.2.2 into work/ex/beta-1.38-1/sources/beta-2019-08-13/reg/pide-rs/0.2.2
[INFO] validating manifest of pide-rs-0.2.2 on toolchain 1.37.0
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of pide-rs-0.2.2 on toolchain beta-2019-08-13
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing pide-rs-0.2.2
[INFO] finished frobbing pide-rs-0.2.2
[INFO] frobbed toml for pide-rs-0.2.2 written to work/ex/beta-1.38-1/sources/1.37.0/reg/pide-rs/0.2.2/Cargo.toml
[INFO] started frobbing pide-rs-0.2.2
[INFO] finished frobbing pide-rs-0.2.2
[INFO] frobbed toml for pide-rs-0.2.2 written to work/ex/beta-1.38-1/sources/beta-2019-08-13/reg/pide-rs/0.2.2/Cargo.toml
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] testing pide-rs-0.2.2 against 1.37.0 for beta-1.38-1
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-2/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/reg/pide-rs/0.2.2:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "build" "--frozen"`
[INFO] [stdout] b56e36cd3c798ffbbb9acd6ada13de3c88a2f5c9700fdb98abee3c7f453e2c17
[INFO] running `"docker" "start" "-a" "b56e36cd3c798ffbbb9acd6ada13de3c88a2f5c9700fdb98abee3c7f453e2c17"`
[INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other binary targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a binary target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/src/main.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobins = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `pide`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]    Compiling uuid v0.4.0
[INFO] [stderr]    Compiling pide-rs v0.2.2 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.30s
[INFO] running `"docker" "inspect" "b56e36cd3c798ffbbb9acd6ada13de3c88a2f5c9700fdb98abee3c7f453e2c17"`
[INFO] running `"docker" "rm" "-f" "b56e36cd3c798ffbbb9acd6ada13de3c88a2f5c9700fdb98abee3c7f453e2c17"`
[INFO] [stdout] b56e36cd3c798ffbbb9acd6ada13de3c88a2f5c9700fdb98abee3c7f453e2c17
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-2/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/reg/pide-rs/0.2.2:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "test" "--frozen" "--no-run"`
[INFO] [stdout] 9b40212cae185cfbd5955b6dc0b53b7b87b0cc58de9d7ed8c1296a1e19c7c4bb
[INFO] running `"docker" "start" "-a" "9b40212cae185cfbd5955b6dc0b53b7b87b0cc58de9d7ed8c1296a1e19c7c4bb"`
[INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other binary targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a binary target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/src/main.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobins = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `pide`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]    Compiling pide-rs v0.2.2 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.66s
[INFO] running `"docker" "inspect" "9b40212cae185cfbd5955b6dc0b53b7b87b0cc58de9d7ed8c1296a1e19c7c4bb"`
[INFO] running `"docker" "rm" "-f" "9b40212cae185cfbd5955b6dc0b53b7b87b0cc58de9d7ed8c1296a1e19c7c4bb"`
[INFO] [stdout] 9b40212cae185cfbd5955b6dc0b53b7b87b0cc58de9d7ed8c1296a1e19c7c4bb
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-2/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/reg/pide-rs/0.2.2:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "test" "--frozen"`
[INFO] [stdout] 46e4eaa68d2ea91d3709eced70b7ba71c69021be4f6de50eec9fed7256bdd911
[INFO] running `"docker" "start" "-a" "46e4eaa68d2ea91d3709eced70b7ba71c69021be4f6de50eec9fed7256bdd911"`
[INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other binary targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a binary target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/src/main.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobins = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `pide`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
[INFO] [stderr]      Running /opt/crater/target/debug/deps/pide-2eba46dea46ef01f
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] running `"docker" "inspect" "46e4eaa68d2ea91d3709eced70b7ba71c69021be4f6de50eec9fed7256bdd911"`
[INFO] running `"docker" "rm" "-f" "46e4eaa68d2ea91d3709eced70b7ba71c69021be4f6de50eec9fed7256bdd911"`
[INFO] [stdout] 46e4eaa68d2ea91d3709eced70b7ba71c69021be4f6de50eec9fed7256bdd911