Nov 18 12:26:32.703 INFO testing google-appsactivity1-cli-1.0.7+20171207 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 12:26:32.704 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-0/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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:26:33.087 INFO [stdout] 67abdc5bd2e2cf092cd2d924a3c33940950ace01148dd6a3dd47a38f883ae206
Nov 18 12:26:33.094 INFO running `"docker" "start" "-a" "67abdc5bd2e2cf092cd2d924a3c33940950ace01148dd6a3dd47a38f883ae206"`
Nov 18 12:26:34.830 INFO [stderr] usermod: no changes
Nov 18 12:26:34.883 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:26:34.883 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:26:34.883 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:26:34.883 INFO [stderr] files will be included as a binary target:
Nov 18 12:26:34.883 INFO [stderr] 
Nov 18 12:26:34.883 INFO [stderr] * /source/src/main.rs
Nov 18 12:26:34.883 INFO [stderr] 
Nov 18 12:26:34.883 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:26:34.883 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:26:34.883 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:26:34.883 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:26:34.883 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:26:34.883 INFO [stderr] 
Nov 18 12:26:34.883 INFO [stderr] For more information on this warning you can consult
Nov 18 12:26:34.883 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:26:34.883 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `appsactivity1`,
Nov 18 12:26:34.883 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:26:35.057 INFO [stderr]    Compiling google-appsactivity1 v1.0.8+20181011
Nov 18 12:26:40.698 INFO [stderr]    Compiling google-appsactivity1-cli v1.0.7+20171207 (/source)
Nov 18 12:26:54.659 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 19.80s
Nov 18 12:26:54.684 INFO [stderr] su: No module specific data is present
Nov 18 12:26:56.156 INFO running `"docker" "inspect" "67abdc5bd2e2cf092cd2d924a3c33940950ace01148dd6a3dd47a38f883ae206"`
Nov 18 12:26:56.591 INFO running `"docker" "rm" "-f" "67abdc5bd2e2cf092cd2d924a3c33940950ace01148dd6a3dd47a38f883ae206"`
Nov 18 12:26:56.915 INFO [stdout] 67abdc5bd2e2cf092cd2d924a3c33940950ace01148dd6a3dd47a38f883ae206
Nov 18 12:26:56.920 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-0/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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:26:57.383 INFO [stdout] 2cc1d221eedab8494988526598d991aa809f868f6339597301f1593c9aed1b59
Nov 18 12:26:57.386 INFO running `"docker" "start" "-a" "2cc1d221eedab8494988526598d991aa809f868f6339597301f1593c9aed1b59"`
Nov 18 12:26:59.518 INFO [stderr] usermod: no changes
Nov 18 12:26:59.595 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:26:59.595 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:26:59.595 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:26:59.595 INFO [stderr] files will be included as a binary target:
Nov 18 12:26:59.595 INFO [stderr] 
Nov 18 12:26:59.595 INFO [stderr] * /source/src/main.rs
Nov 18 12:26:59.595 INFO [stderr] 
Nov 18 12:26:59.595 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:26:59.595 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:26:59.595 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:26:59.595 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:26:59.595 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:26:59.595 INFO [stderr] 
Nov 18 12:26:59.595 INFO [stderr] For more information on this warning you can consult
Nov 18 12:26:59.595 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:26:59.595 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `appsactivity1`,
Nov 18 12:26:59.595 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:26:59.838 INFO [stderr]    Compiling google-appsactivity1-cli v1.0.7+20171207 (/source)
Nov 18 12:27:05.108 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 5.56s
Nov 18 12:27:05.127 INFO [stderr] su: No module specific data is present
Nov 18 12:27:06.473 INFO running `"docker" "inspect" "2cc1d221eedab8494988526598d991aa809f868f6339597301f1593c9aed1b59"`
Nov 18 12:27:06.909 INFO running `"docker" "rm" "-f" "2cc1d221eedab8494988526598d991aa809f868f6339597301f1593c9aed1b59"`
Nov 18 12:27:07.218 INFO [stdout] 2cc1d221eedab8494988526598d991aa809f868f6339597301f1593c9aed1b59
Nov 18 12:27:07.224 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-0/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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:27:07.732 INFO [stdout] f4be7376938f775b2eece6643226d22bd46e5505611c9f99fc50d2c5a3aaf4e3
Nov 18 12:27:07.734 INFO running `"docker" "start" "-a" "f4be7376938f775b2eece6643226d22bd46e5505611c9f99fc50d2c5a3aaf4e3"`
Nov 18 12:27:09.860 INFO [stderr] usermod: no changes
Nov 18 12:27:09.911 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:27:09.911 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:27:09.911 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:27:09.911 INFO [stderr] files will be included as a binary target:
Nov 18 12:27:09.911 INFO [stderr] 
Nov 18 12:27:09.911 INFO [stderr] * /source/src/main.rs
Nov 18 12:27:09.911 INFO [stderr] 
Nov 18 12:27:09.911 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:27:09.911 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:27:09.911 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:27:09.911 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:27:09.911 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:27:09.911 INFO [stderr] 
Nov 18 12:27:09.911 INFO [stderr] For more information on this warning you can consult
Nov 18 12:27:09.911 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:27:09.911 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `appsactivity1`,
Nov 18 12:27:09.911 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:27:10.099 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.21s
Nov 18 12:27:10.111 INFO [stderr]      Running /target/debug/deps/appsactivity1-1346e8e7279de790
Nov 18 12:27:10.111 INFO [stdout] 
Nov 18 12:27:10.111 INFO [stdout] running 0 tests
Nov 18 12:27:10.112 INFO [stdout] 
Nov 18 12:27:10.112 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 12:27:10.112 INFO [stdout] 
Nov 18 12:27:10.114 INFO [stderr] su: No module specific data is present
Nov 18 12:27:11.106 INFO running `"docker" "inspect" "f4be7376938f775b2eece6643226d22bd46e5505611c9f99fc50d2c5a3aaf4e3"`
Nov 18 12:27:11.437 INFO running `"docker" "rm" "-f" "f4be7376938f775b2eece6643226d22bd46e5505611c9f99fc50d2c5a3aaf4e3"`
Nov 18 12:27:11.739 INFO [stdout] f4be7376938f775b2eece6643226d22bd46e5505611c9f99fc50d2c5a3aaf4e3