Nov 18 12:01:16.120 INFO testing google-coordinate1-cli-1.0.7+20150811 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 12:01:16.121 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-6/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/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 12:01:16.539 INFO [stdout] 49ead405c85018b3ebc16026f4dceaaabfce16ae82e071f1971d58c2943ec3db
Nov 18 12:01:16.545 INFO running `"docker" "start" "-a" "49ead405c85018b3ebc16026f4dceaaabfce16ae82e071f1971d58c2943ec3db"`
Nov 18 12:01:18.107 INFO [stderr] usermod: no changes
Nov 18 12:01:18.175 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:01:18.175 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:01:18.175 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:01:18.175 INFO [stderr] files will be included as a binary target:
Nov 18 12:01:18.175 INFO [stderr] 
Nov 18 12:01:18.175 INFO [stderr] * /source/src/main.rs
Nov 18 12:01:18.175 INFO [stderr] 
Nov 18 12:01:18.175 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:01:18.175 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:01:18.175 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:01:18.175 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:01:18.175 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:01:18.175 INFO [stderr] 
Nov 18 12:01:18.175 INFO [stderr] For more information on this warning you can consult
Nov 18 12:01:18.175 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:01:18.175 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `coordinate1`,
Nov 18 12:01:18.175 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:01:18.387 INFO [stderr]    Compiling google-coordinate1 v1.0.8+20150811
Nov 18 12:01:24.992 INFO [stderr]    Compiling google-coordinate1-cli v1.0.7+20150811 (/source)
Nov 18 12:01:44.540 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 26.41s
Nov 18 12:01:44.555 INFO [stderr] su: No module specific data is present
Nov 18 12:01:45.923 INFO running `"docker" "inspect" "49ead405c85018b3ebc16026f4dceaaabfce16ae82e071f1971d58c2943ec3db"`
Nov 18 12:01:46.199 INFO running `"docker" "rm" "-f" "49ead405c85018b3ebc16026f4dceaaabfce16ae82e071f1971d58c2943ec3db"`
Nov 18 12:01:46.583 INFO [stdout] 49ead405c85018b3ebc16026f4dceaaabfce16ae82e071f1971d58c2943ec3db
Nov 18 12:01:46.586 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-6/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/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 12:01:47.045 INFO [stdout] c83e58f19f98dc2d84f4320331131fa4dae0bd7588173455fac0e1d429c5013a
Nov 18 12:01:47.048 INFO running `"docker" "start" "-a" "c83e58f19f98dc2d84f4320331131fa4dae0bd7588173455fac0e1d429c5013a"`
Nov 18 12:01:48.619 INFO [stderr] usermod: no changes
Nov 18 12:01:48.707 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:01:48.707 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:01:48.707 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:01:48.707 INFO [stderr] files will be included as a binary target:
Nov 18 12:01:48.707 INFO [stderr] 
Nov 18 12:01:48.707 INFO [stderr] * /source/src/main.rs
Nov 18 12:01:48.707 INFO [stderr] 
Nov 18 12:01:48.707 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:01:48.707 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:01:48.707 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:01:48.707 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:01:48.707 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:01:48.707 INFO [stderr] 
Nov 18 12:01:48.707 INFO [stderr] For more information on this warning you can consult
Nov 18 12:01:48.707 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:01:48.707 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `coordinate1`,
Nov 18 12:01:48.707 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:01:48.885 INFO [stderr]    Compiling google-coordinate1-cli v1.0.7+20150811 (/source)
Nov 18 12:01:54.536 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 5.89s
Nov 18 12:01:54.559 INFO [stderr] su: No module specific data is present
Nov 18 12:01:55.575 INFO running `"docker" "inspect" "c83e58f19f98dc2d84f4320331131fa4dae0bd7588173455fac0e1d429c5013a"`
Nov 18 12:01:55.885 INFO running `"docker" "rm" "-f" "c83e58f19f98dc2d84f4320331131fa4dae0bd7588173455fac0e1d429c5013a"`
Nov 18 12:01:56.215 INFO [stdout] c83e58f19f98dc2d84f4320331131fa4dae0bd7588173455fac0e1d429c5013a
Nov 18 12:01:56.225 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-6/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/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 12:01:56.567 INFO [stdout] b52fb167a57a72e8b9e65c02b71d3c9b1b1b7534ff615d43fa44f729e2c3345a
Nov 18 12:01:56.569 INFO running `"docker" "start" "-a" "b52fb167a57a72e8b9e65c02b71d3c9b1b1b7534ff615d43fa44f729e2c3345a"`
Nov 18 12:01:57.927 INFO [stderr] usermod: no changes
Nov 18 12:01:57.983 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:01:57.984 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:01:57.984 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:01:57.984 INFO [stderr] files will be included as a binary target:
Nov 18 12:01:57.984 INFO [stderr] 
Nov 18 12:01:57.985 INFO [stderr] * /source/src/main.rs
Nov 18 12:01:57.985 INFO [stderr] 
Nov 18 12:01:57.985 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:01:57.986 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:01:57.986 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:01:57.986 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:01:57.986 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:01:57.987 INFO [stderr] 
Nov 18 12:01:57.987 INFO [stderr] For more information on this warning you can consult
Nov 18 12:01:57.987 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:01:57.988 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `coordinate1`,
Nov 18 12:01:57.988 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:01:58.203 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.25s
Nov 18 12:01:58.219 INFO [stderr]      Running /target/debug/deps/coordinate1-b97ebfb8d08c5889
Nov 18 12:01:58.231 INFO [stderr] su: No module specific data is present
Nov 18 12:01:58.232 INFO [stdout] 
Nov 18 12:01:58.232 INFO [stdout] running 0 tests
Nov 18 12:01:58.232 INFO [stdout] 
Nov 18 12:01:58.232 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 12:01:58.233 INFO [stdout] 
Nov 18 12:01:58.807 INFO running `"docker" "inspect" "b52fb167a57a72e8b9e65c02b71d3c9b1b1b7534ff615d43fa44f729e2c3345a"`
Nov 18 12:01:59.059 INFO running `"docker" "rm" "-f" "b52fb167a57a72e8b9e65c02b71d3c9b1b1b7534ff615d43fa44f729e2c3345a"`
Nov 18 12:01:59.379 INFO [stdout] b52fb167a57a72e8b9e65c02b71d3c9b1b1b7534ff615d43fa44f729e2c3345a