Nov 18 11:13:53.906 INFO testing google-fitness1-cli-1.0.7+20170922 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 18 11:13:53.907 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/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 +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-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 11:13:54.371 INFO [stdout] 26518544f52816ec29d383be779fae93dbd80a9c5e887acf4748b53717c45861
Nov 18 11:13:54.374 INFO running `"docker" "start" "-a" "26518544f52816ec29d383be779fae93dbd80a9c5e887acf4748b53717c45861"`
Nov 18 11:13:56.445 INFO [stderr] usermod: no changes
Nov 18 11:13:56.535 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 11:13:56.535 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 11:13:56.535 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 11:13:56.535 INFO [stderr] files will be included as a binary target:
Nov 18 11:13:56.535 INFO [stderr] 
Nov 18 11:13:56.535 INFO [stderr] * /source/src/main.rs
Nov 18 11:13:56.535 INFO [stderr] 
Nov 18 11:13:56.535 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 11:13:56.535 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 11:13:56.535 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 11:13:56.535 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 11:13:56.535 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 11:13:56.535 INFO [stderr] 
Nov 18 11:13:56.535 INFO [stderr] For more information on this warning you can consult
Nov 18 11:13:56.535 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 11:13:56.535 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `fitness1`,
Nov 18 11:13:56.535 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 11:13:56.721 INFO [stderr]    Compiling google-fitness1 v1.0.8+20170922
Nov 18 11:14:03.780 INFO [stderr]    Compiling google-fitness1-cli v1.0.7+20170922 (/source)
Nov 18 11:14:23.755 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 27.29s
Nov 18 11:14:23.769 INFO [stderr] su: No module specific data is present
Nov 18 11:14:24.803 INFO running `"docker" "inspect" "26518544f52816ec29d383be779fae93dbd80a9c5e887acf4748b53717c45861"`
Nov 18 11:14:25.193 INFO running `"docker" "rm" "-f" "26518544f52816ec29d383be779fae93dbd80a9c5e887acf4748b53717c45861"`
Nov 18 11:14:25.543 INFO [stdout] 26518544f52816ec29d383be779fae93dbd80a9c5e887acf4748b53717c45861
Nov 18 11:14:25.553 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/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 +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-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 11:14:26.032 INFO [stdout] 36933871c1b88d7a62809fe333dfd1005b747cd0406ea22db1fef97e3d8b715c
Nov 18 11:14:26.035 INFO running `"docker" "start" "-a" "36933871c1b88d7a62809fe333dfd1005b747cd0406ea22db1fef97e3d8b715c"`
Nov 18 11:14:28.028 INFO [stderr] usermod: no changes
Nov 18 11:14:28.095 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 11:14:28.095 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 11:14:28.095 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 11:14:28.095 INFO [stderr] files will be included as a binary target:
Nov 18 11:14:28.095 INFO [stderr] 
Nov 18 11:14:28.095 INFO [stderr] * /source/src/main.rs
Nov 18 11:14:28.095 INFO [stderr] 
Nov 18 11:14:28.095 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 11:14:28.095 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 11:14:28.095 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 11:14:28.095 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 11:14:28.095 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 11:14:28.095 INFO [stderr] 
Nov 18 11:14:28.095 INFO [stderr] For more information on this warning you can consult
Nov 18 11:14:28.095 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 11:14:28.095 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `fitness1`,
Nov 18 11:14:28.095 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 11:14:28.283 INFO [stderr]    Compiling google-fitness1-cli v1.0.7+20170922 (/source)
Nov 18 11:14:34.103 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.05s
Nov 18 11:14:34.116 INFO [stderr] su: No module specific data is present
Nov 18 11:14:35.387 INFO running `"docker" "inspect" "36933871c1b88d7a62809fe333dfd1005b747cd0406ea22db1fef97e3d8b715c"`
Nov 18 11:14:35.715 INFO running `"docker" "rm" "-f" "36933871c1b88d7a62809fe333dfd1005b747cd0406ea22db1fef97e3d8b715c"`
Nov 18 11:14:35.965 INFO [stdout] 36933871c1b88d7a62809fe333dfd1005b747cd0406ea22db1fef97e3d8b715c
Nov 18 11:14:35.973 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/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 +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-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 11:14:36.385 INFO [stdout] 41831749d3a7007a4a200efb9a8c3a97c3e5e3e43067b349eaa966fc8be1a7b9
Nov 18 11:14:36.387 INFO running `"docker" "start" "-a" "41831749d3a7007a4a200efb9a8c3a97c3e5e3e43067b349eaa966fc8be1a7b9"`
Nov 18 11:14:37.896 INFO [stderr] usermod: no changes
Nov 18 11:14:37.985 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 11:14:37.985 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 11:14:37.985 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 11:14:37.985 INFO [stderr] files will be included as a binary target:
Nov 18 11:14:37.985 INFO [stderr] 
Nov 18 11:14:37.985 INFO [stderr] * /source/src/main.rs
Nov 18 11:14:37.985 INFO [stderr] 
Nov 18 11:14:37.985 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 11:14:37.985 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 11:14:37.985 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 11:14:37.985 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 11:14:37.985 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 11:14:37.985 INFO [stderr] 
Nov 18 11:14:37.985 INFO [stderr] For more information on this warning you can consult
Nov 18 11:14:37.985 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 11:14:37.985 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `fitness1`,
Nov 18 11:14:37.985 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 11:14:38.160 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.23s
Nov 18 11:14:38.205 INFO [stderr]      Running /target/debug/deps/fitness1-3f95634cd24bc812
Nov 18 11:14:38.208 INFO [stdout] 
Nov 18 11:14:38.208 INFO [stdout] running 0 tests
Nov 18 11:14:38.209 INFO [stdout] 
Nov 18 11:14:38.210 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 11:14:38.210 INFO [stdout] 
Nov 18 11:14:38.214 INFO [stderr] su: No module specific data is present
Nov 18 11:14:39.129 INFO running `"docker" "inspect" "41831749d3a7007a4a200efb9a8c3a97c3e5e3e43067b349eaa966fc8be1a7b9"`
Nov 18 11:14:39.448 INFO running `"docker" "rm" "-f" "41831749d3a7007a4a200efb9a8c3a97c3e5e3e43067b349eaa966fc8be1a7b9"`
Nov 18 11:14:39.759 INFO [stdout] 41831749d3a7007a4a200efb9a8c3a97c3e5e3e43067b349eaa966fc8be1a7b9