Nov 16 22:24:59.077 INFO testing kindlychung/rustbook-phrases against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 16 22:24:59.078 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 16 22:24:59.525 INFO [stdout] b6ebd771a4fe40d639e2a686bcac4ed7287a74fc8c692c98c83a0c6a2a9825d3
Nov 16 22:24:59.529 INFO running `"docker" "start" "-a" "b6ebd771a4fe40d639e2a686bcac4ed7287a74fc8c692c98c83a0c6a2a9825d3"`
Nov 16 22:25:01.551 INFO [stderr] usermod: no changes
Nov 16 22:25:01.607 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 16 22:25:01.607 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 16 22:25:01.607 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 16 22:25:01.607 INFO [stderr] files will be included as a binary target:
Nov 16 22:25:01.607 INFO [stderr] 
Nov 16 22:25:01.607 INFO [stderr] * /source/src/main.rs
Nov 16 22:25:01.607 INFO [stderr] 
Nov 16 22:25:01.607 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 16 22:25:01.607 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 16 22:25:01.607 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 16 22:25:01.607 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 16 22:25:01.607 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 16 22:25:01.607 INFO [stderr] 
Nov 16 22:25:01.607 INFO [stderr] For more information on this warning you can consult
Nov 16 22:25:01.607 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 16 22:25:01.607 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `usephrases`,
Nov 16 22:25:01.607 INFO [stderr] please set bin.path in Cargo.toml
Nov 16 22:25:01.619 INFO [stderr]    Compiling phrases v0.0.1 (/source)
Nov 16 22:25:03.024 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.45s
Nov 16 22:25:03.033 INFO [stderr] su: No module specific data is present
Nov 16 22:25:04.035 INFO running `"docker" "inspect" "b6ebd771a4fe40d639e2a686bcac4ed7287a74fc8c692c98c83a0c6a2a9825d3"`
Nov 16 22:25:04.277 INFO running `"docker" "rm" "-f" "b6ebd771a4fe40d639e2a686bcac4ed7287a74fc8c692c98c83a0c6a2a9825d3"`
Nov 16 22:25:04.614 INFO [stdout] b6ebd771a4fe40d639e2a686bcac4ed7287a74fc8c692c98c83a0c6a2a9825d3
Nov 16 22:25:04.616 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 16 22:25:04.931 INFO [stdout] 49e2edc276445537a983297b5ce18e7f29920b8c9557739e34f6b0796620706a
Nov 16 22:25:04.934 INFO running `"docker" "start" "-a" "49e2edc276445537a983297b5ce18e7f29920b8c9557739e34f6b0796620706a"`
Nov 16 22:25:06.387 INFO [stderr] usermod: no changes
Nov 16 22:25:06.452 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 16 22:25:06.452 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 16 22:25:06.452 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 16 22:25:06.452 INFO [stderr] files will be included as a binary target:
Nov 16 22:25:06.452 INFO [stderr] 
Nov 16 22:25:06.452 INFO [stderr] * /source/src/main.rs
Nov 16 22:25:06.452 INFO [stderr] 
Nov 16 22:25:06.452 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 16 22:25:06.452 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 16 22:25:06.452 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 16 22:25:06.452 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 16 22:25:06.452 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 16 22:25:06.452 INFO [stderr] 
Nov 16 22:25:06.452 INFO [stderr] For more information on this warning you can consult
Nov 16 22:25:06.452 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 16 22:25:06.452 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `usephrases`,
Nov 16 22:25:06.452 INFO [stderr] please set bin.path in Cargo.toml
Nov 16 22:25:06.455 INFO [stderr]    Compiling phrases v0.0.1 (/source)
Nov 16 22:25:07.651 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.23s
Nov 16 22:25:07.657 INFO [stderr] su: No module specific data is present
Nov 16 22:25:09.059 INFO running `"docker" "inspect" "49e2edc276445537a983297b5ce18e7f29920b8c9557739e34f6b0796620706a"`
Nov 16 22:25:09.357 INFO running `"docker" "rm" "-f" "49e2edc276445537a983297b5ce18e7f29920b8c9557739e34f6b0796620706a"`
Nov 16 22:25:09.703 INFO [stdout] 49e2edc276445537a983297b5ce18e7f29920b8c9557739e34f6b0796620706a
Nov 16 22:25:09.709 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 16 22:25:10.175 INFO [stdout] 6affc805d5b8fb23cc3e1e4e8a75da6a01cf438dddb848072c5a314f34e82dd8
Nov 16 22:25:10.177 INFO running `"docker" "start" "-a" "6affc805d5b8fb23cc3e1e4e8a75da6a01cf438dddb848072c5a314f34e82dd8"`
Nov 16 22:25:12.119 INFO [stderr] usermod: no changes
Nov 16 22:25:12.179 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 16 22:25:12.179 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 16 22:25:12.179 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 16 22:25:12.179 INFO [stderr] files will be included as a binary target:
Nov 16 22:25:12.179 INFO [stderr] 
Nov 16 22:25:12.179 INFO [stderr] * /source/src/main.rs
Nov 16 22:25:12.179 INFO [stderr] 
Nov 16 22:25:12.179 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 16 22:25:12.179 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 16 22:25:12.179 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 16 22:25:12.179 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 16 22:25:12.179 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 16 22:25:12.179 INFO [stderr] 
Nov 16 22:25:12.179 INFO [stderr] For more information on this warning you can consult
Nov 16 22:25:12.179 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 16 22:25:12.179 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `usephrases`,
Nov 16 22:25:12.179 INFO [stderr] please set bin.path in Cargo.toml
Nov 16 22:25:12.179 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.03s
Nov 16 22:25:12.191 INFO [stderr]      Running /target/debug/deps/phrases-d425ab63625b212b
Nov 16 22:25:12.191 INFO [stderr]      Running /target/debug/deps/usephrases-7ea0d360340e6085
Nov 16 22:25:12.191 INFO [stdout] 
Nov 16 22:25:12.191 INFO [stdout] running 0 tests
Nov 16 22:25:12.191 INFO [stdout] 
Nov 16 22:25:12.191 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 16 22:25:12.191 INFO [stdout] 
Nov 16 22:25:12.199 INFO [stdout] 
Nov 16 22:25:12.199 INFO [stdout] running 0 tests
Nov 16 22:25:12.199 INFO [stdout] 
Nov 16 22:25:12.199 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 16 22:25:12.199 INFO [stdout] 
Nov 16 22:25:12.199 INFO [stderr]    Doc-tests phrases
Nov 16 22:25:12.599 INFO [stdout] 
Nov 16 22:25:12.599 INFO [stdout] running 0 tests
Nov 16 22:25:12.599 INFO [stdout] 
Nov 16 22:25:12.599 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 16 22:25:12.599 INFO [stdout] 
Nov 16 22:25:12.604 INFO [stderr] su: No module specific data is present
Nov 16 22:25:13.817 INFO running `"docker" "inspect" "6affc805d5b8fb23cc3e1e4e8a75da6a01cf438dddb848072c5a314f34e82dd8"`
Nov 16 22:25:14.109 INFO running `"docker" "rm" "-f" "6affc805d5b8fb23cc3e1e4e8a75da6a01cf438dddb848072c5a314f34e82dd8"`
Nov 16 22:25:14.515 INFO [stdout] 6affc805d5b8fb23cc3e1e4e8a75da6a01cf438dddb848072c5a314f34e82dd8