Nov 18 17:40:49.181 INFO testing cli-utils-0.1.0 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 17:40:49.181 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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 18 17:40:49.379 INFO [stdout] b0c5e16d7b7243b9277d1ac918a030a458a090bd25a078841cbd8851917ac250
Nov 18 17:40:49.385 INFO running `"docker" "start" "-a" "b0c5e16d7b7243b9277d1ac918a030a458a090bd25a078841cbd8851917ac250"`
Nov 18 17:40:49.971 INFO [stderr] usermod: no changes
Nov 18 17:40:50.011 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 17:40:50.011 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 17:40:50.011 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 17:40:50.011 INFO [stderr] files will be included as a binary target:
Nov 18 17:40:50.011 INFO [stderr] 
Nov 18 17:40:50.011 INFO [stderr] * /source/src/bin/execute.rs
Nov 18 17:40:50.011 INFO [stderr] 
Nov 18 17:40:50.011 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 17:40:50.011 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 17:40:50.011 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 17:40:50.011 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 17:40:50.011 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 17:40:50.011 INFO [stderr] 
Nov 18 17:40:50.011 INFO [stderr] For more information on this warning you can consult
Nov 18 17:40:50.011 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 17:40:50.043 INFO [stderr]    Compiling cli-utils v0.1.0 (/source)
Nov 18 17:40:51.929 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.94s
Nov 18 17:40:51.933 INFO [stderr] su: No module specific data is present
Nov 18 17:40:52.461 INFO running `"docker" "inspect" "b0c5e16d7b7243b9277d1ac918a030a458a090bd25a078841cbd8851917ac250"`
Nov 18 17:40:52.730 INFO running `"docker" "rm" "-f" "b0c5e16d7b7243b9277d1ac918a030a458a090bd25a078841cbd8851917ac250"`
Nov 18 17:40:52.895 INFO [stdout] b0c5e16d7b7243b9277d1ac918a030a458a090bd25a078841cbd8851917ac250
Nov 18 17:40:52.898 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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 18 17:40:53.211 INFO [stdout] 6692b85e351e0eca920de41b7d1394d667a929912cb264b2dc71dfc2cd2dca6f
Nov 18 17:40:53.214 INFO running `"docker" "start" "-a" "6692b85e351e0eca920de41b7d1394d667a929912cb264b2dc71dfc2cd2dca6f"`
Nov 18 17:40:54.239 INFO [stderr] usermod: no changes
Nov 18 17:40:54.270 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 17:40:54.271 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 17:40:54.271 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 17:40:54.271 INFO [stderr] files will be included as a binary target:
Nov 18 17:40:54.271 INFO [stderr] 
Nov 18 17:40:54.271 INFO [stderr] * /source/src/bin/execute.rs
Nov 18 17:40:54.271 INFO [stderr] 
Nov 18 17:40:54.271 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 17:40:54.271 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 17:40:54.271 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 17:40:54.271 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 17:40:54.271 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 17:40:54.271 INFO [stderr] 
Nov 18 17:40:54.271 INFO [stderr] For more information on this warning you can consult
Nov 18 17:40:54.271 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 17:40:54.292 INFO [stderr]    Compiling cli-utils v0.1.0 (/source)
Nov 18 17:40:55.330 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.07s
Nov 18 17:40:55.334 INFO [stderr] su: No module specific data is present
Nov 18 17:40:55.691 INFO running `"docker" "inspect" "6692b85e351e0eca920de41b7d1394d667a929912cb264b2dc71dfc2cd2dca6f"`
Nov 18 17:40:55.780 INFO running `"docker" "rm" "-f" "6692b85e351e0eca920de41b7d1394d667a929912cb264b2dc71dfc2cd2dca6f"`
Nov 18 17:40:55.913 INFO [stdout] 6692b85e351e0eca920de41b7d1394d667a929912cb264b2dc71dfc2cd2dca6f
Nov 18 17:40:55.917 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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 18 17:40:56.147 INFO [stdout] 2a0cd357cf3e13b9e6b1040f17494fc03ac167ff97f00be85a95cb1620a6ded8
Nov 18 17:40:56.152 INFO running `"docker" "start" "-a" "2a0cd357cf3e13b9e6b1040f17494fc03ac167ff97f00be85a95cb1620a6ded8"`
Nov 18 17:40:56.633 INFO [stderr] usermod: no changes
Nov 18 17:40:56.663 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 17:40:56.663 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 17:40:56.663 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 17:40:56.663 INFO [stderr] files will be included as a binary target:
Nov 18 17:40:56.663 INFO [stderr] 
Nov 18 17:40:56.663 INFO [stderr] * /source/src/bin/execute.rs
Nov 18 17:40:56.663 INFO [stderr] 
Nov 18 17:40:56.663 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 17:40:56.663 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 17:40:56.663 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 17:40:56.663 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 17:40:56.663 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 17:40:56.663 INFO [stderr] 
Nov 18 17:40:56.663 INFO [stderr] For more information on this warning you can consult
Nov 18 17:40:56.663 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 17:40:56.675 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
Nov 18 17:40:56.677 INFO [stderr]      Running /target/debug/deps/loop-e88b39b508fc1a5e
Nov 18 17:40:56.680 INFO [stdout] 
Nov 18 17:40:56.680 INFO [stdout] running 0 tests
Nov 18 17:40:56.680 INFO [stdout] 
Nov 18 17:40:56.680 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 17:40:56.680 INFO [stdout] 
Nov 18 17:40:56.681 INFO [stderr]      Running /target/debug/deps/timer-7978bea29202def3
Nov 18 17:40:56.684 INFO [stdout] 
Nov 18 17:40:56.684 INFO [stdout] running 0 tests
Nov 18 17:40:56.684 INFO [stdout] 
Nov 18 17:40:56.684 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 17:40:56.684 INFO [stdout] 
Nov 18 17:40:56.686 INFO [stderr] su: No module specific data is present
Nov 18 17:40:56.995 INFO running `"docker" "inspect" "2a0cd357cf3e13b9e6b1040f17494fc03ac167ff97f00be85a95cb1620a6ded8"`
Nov 18 17:40:57.275 INFO running `"docker" "rm" "-f" "2a0cd357cf3e13b9e6b1040f17494fc03ac167ff97f00be85a95cb1620a6ded8"`
Nov 18 17:40:57.575 INFO [stdout] 2a0cd357cf3e13b9e6b1040f17494fc03ac167ff97f00be85a95cb1620a6ded8