Nov 18 10:54:09.560 INFO testing google-proximitybeacon1_beta1-cli-1.0.7+20171112 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 10:54:09.560 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 10:54:10.069 INFO [stdout] 76333dcaa21e3b63a761aee5c19bc3042e4b509e6df3eef1e3d889057f16cf11
Nov 18 10:54:10.071 INFO running `"docker" "start" "-a" "76333dcaa21e3b63a761aee5c19bc3042e4b509e6df3eef1e3d889057f16cf11"`
Nov 18 10:54:12.162 INFO [stderr] usermod: no changes
Nov 18 10:54:12.247 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:54:12.247 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:54:12.247 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:54:12.247 INFO [stderr] files will be included as a binary target:
Nov 18 10:54:12.247 INFO [stderr] 
Nov 18 10:54:12.247 INFO [stderr] * /source/src/main.rs
Nov 18 10:54:12.247 INFO [stderr] 
Nov 18 10:54:12.247 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:54:12.247 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:54:12.247 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:54:12.247 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:54:12.247 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:54:12.247 INFO [stderr] 
Nov 18 10:54:12.247 INFO [stderr] For more information on this warning you can consult
Nov 18 10:54:12.247 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:54:12.247 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `proximitybeacon1-beta1`,
Nov 18 10:54:12.247 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:54:12.474 INFO [stderr]    Compiling google-proximitybeacon1_beta1 v1.0.8+20181008
Nov 18 10:54:19.293 INFO [stderr]    Compiling google-proximitybeacon1_beta1-cli v1.0.7+20171112 (/source)
Nov 18 10:54:37.879 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 25.68s
Nov 18 10:54:37.903 INFO [stderr] su: No module specific data is present
Nov 18 10:54:38.545 INFO running `"docker" "inspect" "76333dcaa21e3b63a761aee5c19bc3042e4b509e6df3eef1e3d889057f16cf11"`
Nov 18 10:54:38.711 INFO running `"docker" "rm" "-f" "76333dcaa21e3b63a761aee5c19bc3042e4b509e6df3eef1e3d889057f16cf11"`
Nov 18 10:54:38.866 INFO [stdout] 76333dcaa21e3b63a761aee5c19bc3042e4b509e6df3eef1e3d889057f16cf11
Nov 18 10:54:38.866 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 10:54:39.046 INFO [stdout] 6ccdf55e8657a8cbf2d114f200364e6c3fdaf9413750f82e58e648778e8dd7d8
Nov 18 10:54:39.055 INFO running `"docker" "start" "-a" "6ccdf55e8657a8cbf2d114f200364e6c3fdaf9413750f82e58e648778e8dd7d8"`
Nov 18 10:54:39.503 INFO [stderr] usermod: no changes
Nov 18 10:54:39.533 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:54:39.533 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:54:39.533 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:54:39.533 INFO [stderr] files will be included as a binary target:
Nov 18 10:54:39.533 INFO [stderr] 
Nov 18 10:54:39.533 INFO [stderr] * /source/src/main.rs
Nov 18 10:54:39.533 INFO [stderr] 
Nov 18 10:54:39.533 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:54:39.533 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:54:39.533 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:54:39.533 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:54:39.533 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:54:39.533 INFO [stderr] 
Nov 18 10:54:39.533 INFO [stderr] For more information on this warning you can consult
Nov 18 10:54:39.533 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:54:39.533 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `proximitybeacon1-beta1`,
Nov 18 10:54:39.533 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:54:39.673 INFO [stderr]    Compiling google-proximitybeacon1_beta1-cli v1.0.7+20171112 (/source)
Nov 18 10:54:45.099 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 5.57s
Nov 18 10:54:45.110 INFO [stderr] su: No module specific data is present
Nov 18 10:54:45.947 INFO running `"docker" "inspect" "6ccdf55e8657a8cbf2d114f200364e6c3fdaf9413750f82e58e648778e8dd7d8"`
Nov 18 10:54:46.276 INFO running `"docker" "rm" "-f" "6ccdf55e8657a8cbf2d114f200364e6c3fdaf9413750f82e58e648778e8dd7d8"`
Nov 18 10:54:46.618 INFO [stdout] 6ccdf55e8657a8cbf2d114f200364e6c3fdaf9413750f82e58e648778e8dd7d8
Nov 18 10:54:46.625 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 10:54:47.040 INFO [stdout] 98efd624e0425da0bb0c4ae69a211dc3bd8180c8f2501829aee85c9c99130a3b
Nov 18 10:54:47.045 INFO running `"docker" "start" "-a" "98efd624e0425da0bb0c4ae69a211dc3bd8180c8f2501829aee85c9c99130a3b"`
Nov 18 10:54:47.972 INFO [stderr] usermod: no changes
Nov 18 10:54:48.011 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:54:48.011 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:54:48.011 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:54:48.011 INFO [stderr] files will be included as a binary target:
Nov 18 10:54:48.011 INFO [stderr] 
Nov 18 10:54:48.011 INFO [stderr] * /source/src/main.rs
Nov 18 10:54:48.011 INFO [stderr] 
Nov 18 10:54:48.011 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:54:48.011 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:54:48.011 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:54:48.011 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:54:48.011 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:54:48.011 INFO [stderr] 
Nov 18 10:54:48.011 INFO [stderr] For more information on this warning you can consult
Nov 18 10:54:48.011 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:54:48.011 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `proximitybeacon1-beta1`,
Nov 18 10:54:48.011 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:54:48.144 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.14s
Nov 18 10:54:48.161 INFO [stderr]      Running /target/debug/deps/proximitybeacon1_beta1-6f8e47041f2c2a44
Nov 18 10:54:48.165 INFO [stdout] 
Nov 18 10:54:48.165 INFO [stdout] running 0 tests
Nov 18 10:54:48.165 INFO [stdout] 
Nov 18 10:54:48.165 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 10:54:48.165 INFO [stdout] 
Nov 18 10:54:48.172 INFO [stderr] su: No module specific data is present
Nov 18 10:54:48.508 INFO running `"docker" "inspect" "98efd624e0425da0bb0c4ae69a211dc3bd8180c8f2501829aee85c9c99130a3b"`
Nov 18 10:54:48.634 INFO running `"docker" "rm" "-f" "98efd624e0425da0bb0c4ae69a211dc3bd8180c8f2501829aee85c9c99130a3b"`
Nov 18 10:54:48.733 INFO [stdout] 98efd624e0425da0bb0c4ae69a211dc3bd8180c8f2501829aee85c9c99130a3b