Dec 05 17:44:15.710 INFO testing kindlychung/rustbook-phrases against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514
Dec 05 17:44:15.710 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-6/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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"`
Dec 05 17:44:16.182 INFO [stdout] d329b14af7a514fc5f37e78ed6c961d08a307b1df64a48642c297d52b3d4f593
Dec 05 17:44:16.184 INFO running `"docker" "start" "-a" "d329b14af7a514fc5f37e78ed6c961d08a307b1df64a48642c297d52b3d4f593"`
Dec 05 17:44:18.515 INFO [stderr] usermod: no changes
Dec 05 17:44:18.592 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 05 17:44:18.592 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 05 17:44:18.592 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 05 17:44:18.592 INFO [stderr] files will be included as a binary target:
Dec 05 17:44:18.592 INFO [stderr] 
Dec 05 17:44:18.592 INFO [stderr] * /source/src/main.rs
Dec 05 17:44:18.592 INFO [stderr] 
Dec 05 17:44:18.592 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 05 17:44:18.592 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 05 17:44:18.592 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 05 17:44:18.592 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 05 17:44:18.592 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 05 17:44:18.592 INFO [stderr] 
Dec 05 17:44:18.592 INFO [stderr] For more information on this warning you can consult
Dec 05 17:44:18.592 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 05 17:44:18.592 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `usephrases`,
Dec 05 17:44:18.592 INFO [stderr] please set bin.path in Cargo.toml
Dec 05 17:44:18.615 INFO [stderr]    Compiling phrases v0.0.1 (/source)
Dec 05 17:44:19.826 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.27s
Dec 05 17:44:19.829 INFO [stderr] su: No module specific data is present
Dec 05 17:44:21.109 INFO running `"docker" "inspect" "d329b14af7a514fc5f37e78ed6c961d08a307b1df64a48642c297d52b3d4f593"`
Dec 05 17:44:21.296 INFO running `"docker" "rm" "-f" "d329b14af7a514fc5f37e78ed6c961d08a307b1df64a48642c297d52b3d4f593"`
Dec 05 17:44:21.660 INFO [stdout] d329b14af7a514fc5f37e78ed6c961d08a307b1df64a48642c297d52b3d4f593
Dec 05 17:44:21.668 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-6/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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"`
Dec 05 17:44:22.123 INFO [stdout] d5c942907ab8531d1cf48745e5cd49d9c4d683435684ef5d6084e8b5fb4979a4
Dec 05 17:44:22.126 INFO running `"docker" "start" "-a" "d5c942907ab8531d1cf48745e5cd49d9c4d683435684ef5d6084e8b5fb4979a4"`
Dec 05 17:44:23.620 INFO [stderr] usermod: no changes
Dec 05 17:44:23.660 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 05 17:44:23.660 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 05 17:44:23.660 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 05 17:44:23.660 INFO [stderr] files will be included as a binary target:
Dec 05 17:44:23.660 INFO [stderr] 
Dec 05 17:44:23.660 INFO [stderr] * /source/src/main.rs
Dec 05 17:44:23.660 INFO [stderr] 
Dec 05 17:44:23.660 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 05 17:44:23.660 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 05 17:44:23.660 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 05 17:44:23.660 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 05 17:44:23.660 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 05 17:44:23.660 INFO [stderr] 
Dec 05 17:44:23.660 INFO [stderr] For more information on this warning you can consult
Dec 05 17:44:23.660 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 05 17:44:23.660 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `usephrases`,
Dec 05 17:44:23.660 INFO [stderr] please set bin.path in Cargo.toml
Dec 05 17:44:23.670 INFO [stderr]    Compiling phrases v0.0.1 (/source)
Dec 05 17:44:24.589 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.94s
Dec 05 17:44:24.592 INFO [stderr] su: No module specific data is present
Dec 05 17:44:25.195 INFO running `"docker" "inspect" "d5c942907ab8531d1cf48745e5cd49d9c4d683435684ef5d6084e8b5fb4979a4"`
Dec 05 17:44:25.342 INFO running `"docker" "rm" "-f" "d5c942907ab8531d1cf48745e5cd49d9c4d683435684ef5d6084e8b5fb4979a4"`
Dec 05 17:44:25.488 INFO [stdout] d5c942907ab8531d1cf48745e5cd49d9c4d683435684ef5d6084e8b5fb4979a4
Dec 05 17:44:25.494 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-6/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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"`
Dec 05 17:44:25.730 INFO [stdout] 72ac8199c263cc5853c03187f649d1fe331a770df1c0f2e533f3825b147a8461
Dec 05 17:44:25.733 INFO running `"docker" "start" "-a" "72ac8199c263cc5853c03187f649d1fe331a770df1c0f2e533f3825b147a8461"`
Dec 05 17:44:26.406 INFO [stderr] usermod: no changes
Dec 05 17:44:26.432 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 05 17:44:26.432 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 05 17:44:26.432 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 05 17:44:26.432 INFO [stderr] files will be included as a binary target:
Dec 05 17:44:26.432 INFO [stderr] 
Dec 05 17:44:26.432 INFO [stderr] * /source/src/main.rs
Dec 05 17:44:26.432 INFO [stderr] 
Dec 05 17:44:26.432 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 05 17:44:26.432 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 05 17:44:26.432 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 05 17:44:26.432 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 05 17:44:26.432 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 05 17:44:26.432 INFO [stderr] 
Dec 05 17:44:26.432 INFO [stderr] For more information on this warning you can consult
Dec 05 17:44:26.432 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 05 17:44:26.432 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `usephrases`,
Dec 05 17:44:26.432 INFO [stderr] please set bin.path in Cargo.toml
Dec 05 17:44:26.434 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.01s
Dec 05 17:44:26.436 INFO [stderr]      Running /target/debug/deps/phrases-3a10d6deaa6d8f0d
Dec 05 17:44:26.440 INFO [stderr]      Running /target/debug/deps/usephrases-2db83a7ba5253150
Dec 05 17:44:26.440 INFO [stderr]    Doc-tests phrases
Dec 05 17:44:26.440 INFO [stdout] 
Dec 05 17:44:26.440 INFO [stdout] running 0 tests
Dec 05 17:44:26.440 INFO [stdout] 
Dec 05 17:44:26.440 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 05 17:44:26.440 INFO [stdout] 
Dec 05 17:44:26.440 INFO [stdout] 
Dec 05 17:44:26.440 INFO [stdout] running 0 tests
Dec 05 17:44:26.440 INFO [stdout] 
Dec 05 17:44:26.440 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 05 17:44:26.440 INFO [stdout] 
Dec 05 17:44:26.840 INFO [stdout] 
Dec 05 17:44:26.840 INFO [stdout] running 0 tests
Dec 05 17:44:26.840 INFO [stdout] 
Dec 05 17:44:26.840 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 05 17:44:26.840 INFO [stdout] 
Dec 05 17:44:26.847 INFO [stderr] su: No module specific data is present
Dec 05 17:44:27.156 INFO running `"docker" "inspect" "72ac8199c263cc5853c03187f649d1fe331a770df1c0f2e533f3825b147a8461"`
Dec 05 17:44:27.282 INFO running `"docker" "rm" "-f" "72ac8199c263cc5853c03187f649d1fe331a770df1c0f2e533f3825b147a8461"`
Dec 05 17:44:27.414 INFO [stdout] 72ac8199c263cc5853c03187f649d1fe331a770df1c0f2e533f3825b147a8461