Nov 18 12:16:54.872 INFO testing google-cloudfunctions1-cli-1.0.7+20171206 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 12:16:54.872 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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:16:55.320 INFO [stdout] ac2e035adfbea62522bd101f4993a1a9e2ddc724337f5bbd05acfe1321c1fbd4
Nov 18 12:16:55.321 INFO running `"docker" "start" "-a" "ac2e035adfbea62522bd101f4993a1a9e2ddc724337f5bbd05acfe1321c1fbd4"`
Nov 18 12:16:56.674 INFO [stderr] usermod: no changes
Nov 18 12:16:56.723 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:16:56.723 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:16:56.723 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:16:56.723 INFO [stderr] files will be included as a binary target:
Nov 18 12:16:56.723 INFO [stderr] 
Nov 18 12:16:56.723 INFO [stderr] * /source/src/main.rs
Nov 18 12:16:56.723 INFO [stderr] 
Nov 18 12:16:56.723 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:16:56.723 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:16:56.723 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:16:56.723 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:16:56.723 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:16:56.723 INFO [stderr] 
Nov 18 12:16:56.723 INFO [stderr] For more information on this warning you can consult
Nov 18 12:16:56.723 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:16:56.723 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `cloudfunctions1`,
Nov 18 12:16:56.723 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:16:56.907 INFO [stderr]    Compiling google-cloudfunctions1 v1.0.8+20181002
Nov 18 12:17:03.515 INFO [stderr]    Compiling google-cloudfunctions1-cli v1.0.7+20171206 (/source)
Nov 18 12:17:19.403 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 22.70s
Nov 18 12:17:19.415 INFO [stderr] su: No module specific data is present
Nov 18 12:17:20.199 INFO running `"docker" "inspect" "ac2e035adfbea62522bd101f4993a1a9e2ddc724337f5bbd05acfe1321c1fbd4"`
Nov 18 12:17:20.534 INFO running `"docker" "rm" "-f" "ac2e035adfbea62522bd101f4993a1a9e2ddc724337f5bbd05acfe1321c1fbd4"`
Nov 18 12:17:20.947 INFO [stdout] ac2e035adfbea62522bd101f4993a1a9e2ddc724337f5bbd05acfe1321c1fbd4
Nov 18 12:17:20.951 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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:17:21.447 INFO [stdout] 40befd9372adb47202f08222535ef1129bd40987487fe1055d8207501e0474ee
Nov 18 12:17:21.453 INFO running `"docker" "start" "-a" "40befd9372adb47202f08222535ef1129bd40987487fe1055d8207501e0474ee"`
Nov 18 12:17:22.879 INFO [stderr] usermod: no changes
Nov 18 12:17:22.939 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:17:22.939 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:17:22.939 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:17:22.939 INFO [stderr] files will be included as a binary target:
Nov 18 12:17:22.939 INFO [stderr] 
Nov 18 12:17:22.939 INFO [stderr] * /source/src/main.rs
Nov 18 12:17:22.939 INFO [stderr] 
Nov 18 12:17:22.939 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:17:22.939 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:17:22.939 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:17:22.939 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:17:22.939 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:17:22.939 INFO [stderr] 
Nov 18 12:17:22.939 INFO [stderr] For more information on this warning you can consult
Nov 18 12:17:22.939 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:17:22.939 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `cloudfunctions1`,
Nov 18 12:17:22.939 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:17:23.183 INFO [stderr]    Compiling google-cloudfunctions1-cli v1.0.7+20171206 (/source)
Nov 18 12:17:28.942 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.03s
Nov 18 12:17:28.954 INFO [stderr] su: No module specific data is present
Nov 18 12:17:29.634 INFO running `"docker" "inspect" "40befd9372adb47202f08222535ef1129bd40987487fe1055d8207501e0474ee"`
Nov 18 12:17:29.877 INFO running `"docker" "rm" "-f" "40befd9372adb47202f08222535ef1129bd40987487fe1055d8207501e0474ee"`
Nov 18 12:17:30.379 INFO [stdout] 40befd9372adb47202f08222535ef1129bd40987487fe1055d8207501e0474ee
Nov 18 12:17:30.390 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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:17:30.874 INFO [stdout] a12f5a451195ce992c06b5903e5e998e008066a7ae3446f2cde951508bca6a05
Nov 18 12:17:30.883 INFO running `"docker" "start" "-a" "a12f5a451195ce992c06b5903e5e998e008066a7ae3446f2cde951508bca6a05"`
Nov 18 12:17:32.028 INFO [stderr] usermod: no changes
Nov 18 12:17:32.059 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:17:32.059 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:17:32.059 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:17:32.059 INFO [stderr] files will be included as a binary target:
Nov 18 12:17:32.059 INFO [stderr] 
Nov 18 12:17:32.059 INFO [stderr] * /source/src/main.rs
Nov 18 12:17:32.059 INFO [stderr] 
Nov 18 12:17:32.059 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:17:32.059 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:17:32.059 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:17:32.059 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:17:32.059 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:17:32.059 INFO [stderr] 
Nov 18 12:17:32.059 INFO [stderr] For more information on this warning you can consult
Nov 18 12:17:32.059 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:17:32.059 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `cloudfunctions1`,
Nov 18 12:17:32.059 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:17:32.254 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.16s
Nov 18 12:17:32.255 INFO [stderr]      Running /target/debug/deps/cloudfunctions1-2c884ede6cf9cee9
Nov 18 12:17:32.255 INFO [stderr] su: No module specific data is present
Nov 18 12:17:32.255 INFO [stdout] 
Nov 18 12:17:32.255 INFO [stdout] running 0 tests
Nov 18 12:17:32.255 INFO [stdout] 
Nov 18 12:17:32.255 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 12:17:32.255 INFO [stdout] 
Nov 18 12:17:33.031 INFO running `"docker" "inspect" "a12f5a451195ce992c06b5903e5e998e008066a7ae3446f2cde951508bca6a05"`
Nov 18 12:17:33.409 INFO running `"docker" "rm" "-f" "a12f5a451195ce992c06b5903e5e998e008066a7ae3446f2cde951508bca6a05"`
Nov 18 12:17:33.727 INFO [stdout] a12f5a451195ce992c06b5903e5e998e008066a7ae3446f2cde951508bca6a05