Nov 18 10:46:02.329 INFO testing google-spanner1-cli-1.0.7+20171204 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 18 10:46:02.331 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 10:46:02.791 INFO [stdout] e37669ae33c349c9ca54361a5b9dfb88fbbd63b16c4c1e973fa1c8a2d930e11c
Nov 18 10:46:02.794 INFO running `"docker" "start" "-a" "e37669ae33c349c9ca54361a5b9dfb88fbbd63b16c4c1e973fa1c8a2d930e11c"`
Nov 18 10:46:05.321 INFO [stderr] usermod: no changes
Nov 18 10:46:05.375 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:46:05.375 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:46:05.375 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:46:05.375 INFO [stderr] files will be included as a binary target:
Nov 18 10:46:05.375 INFO [stderr] 
Nov 18 10:46:05.375 INFO [stderr] * /source/src/main.rs
Nov 18 10:46:05.375 INFO [stderr] 
Nov 18 10:46:05.375 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:46:05.375 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:46:05.375 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:46:05.375 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:46:05.375 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:46:05.375 INFO [stderr] 
Nov 18 10:46:05.375 INFO [stderr] For more information on this warning you can consult
Nov 18 10:46:05.375 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:46:05.375 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `spanner1`,
Nov 18 10:46:05.375 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:46:05.604 INFO [stderr]    Compiling google-spanner1 v1.0.8+20180920
Nov 18 10:46:17.063 INFO [stderr]    Compiling google-spanner1-cli v1.0.7+20171204 (/source)
Nov 18 10:46:45.059 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 39.71s
Nov 18 10:46:45.087 INFO [stderr] su: No module specific data is present
Nov 18 10:46:46.067 INFO running `"docker" "inspect" "e37669ae33c349c9ca54361a5b9dfb88fbbd63b16c4c1e973fa1c8a2d930e11c"`
Nov 18 10:46:46.325 INFO running `"docker" "rm" "-f" "e37669ae33c349c9ca54361a5b9dfb88fbbd63b16c4c1e973fa1c8a2d930e11c"`
Nov 18 10:46:46.607 INFO [stdout] e37669ae33c349c9ca54361a5b9dfb88fbbd63b16c4c1e973fa1c8a2d930e11c
Nov 18 10:46:46.611 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 10:46:47.040 INFO [stdout] 173b75b8cdc907bc37bd4cf80947a2bc4aed6281ce1dbb29e3f9b15e9ba4b4bd
Nov 18 10:46:47.043 INFO running `"docker" "start" "-a" "173b75b8cdc907bc37bd4cf80947a2bc4aed6281ce1dbb29e3f9b15e9ba4b4bd"`
Nov 18 10:46:48.842 INFO [stderr] usermod: no changes
Nov 18 10:46:48.891 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:46:48.891 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:46:48.891 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:46:48.891 INFO [stderr] files will be included as a binary target:
Nov 18 10:46:48.891 INFO [stderr] 
Nov 18 10:46:48.891 INFO [stderr] * /source/src/main.rs
Nov 18 10:46:48.891 INFO [stderr] 
Nov 18 10:46:48.891 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:46:48.891 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:46:48.891 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:46:48.891 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:46:48.891 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:46:48.891 INFO [stderr] 
Nov 18 10:46:48.891 INFO [stderr] For more information on this warning you can consult
Nov 18 10:46:48.891 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:46:48.891 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `spanner1`,
Nov 18 10:46:48.891 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:46:49.119 INFO [stderr]    Compiling google-spanner1-cli v1.0.7+20171204 (/source)
Nov 18 10:46:55.843 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.97s
Nov 18 10:46:55.872 INFO [stderr] su: No module specific data is present
Nov 18 10:46:56.678 INFO running `"docker" "inspect" "173b75b8cdc907bc37bd4cf80947a2bc4aed6281ce1dbb29e3f9b15e9ba4b4bd"`
Nov 18 10:46:57.147 INFO running `"docker" "rm" "-f" "173b75b8cdc907bc37bd4cf80947a2bc4aed6281ce1dbb29e3f9b15e9ba4b4bd"`
Nov 18 10:46:57.559 INFO [stdout] 173b75b8cdc907bc37bd4cf80947a2bc4aed6281ce1dbb29e3f9b15e9ba4b4bd
Nov 18 10:46:57.569 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 10:46:57.980 INFO [stdout] 8dd2ef442138b5f3a5d2ba7e86a37f88ac59aeadf90e067e3104ba2e240fadaf
Nov 18 10:46:57.983 INFO running `"docker" "start" "-a" "8dd2ef442138b5f3a5d2ba7e86a37f88ac59aeadf90e067e3104ba2e240fadaf"`
Nov 18 10:46:59.330 INFO [stderr] usermod: no changes
Nov 18 10:46:59.379 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:46:59.380 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:46:59.380 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:46:59.380 INFO [stderr] files will be included as a binary target:
Nov 18 10:46:59.381 INFO [stderr] 
Nov 18 10:46:59.381 INFO [stderr] * /source/src/main.rs
Nov 18 10:46:59.381 INFO [stderr] 
Nov 18 10:46:59.382 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:46:59.382 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:46:59.382 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:46:59.382 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:46:59.383 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:46:59.383 INFO [stderr] 
Nov 18 10:46:59.383 INFO [stderr] For more information on this warning you can consult
Nov 18 10:46:59.384 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:46:59.384 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `spanner1`,
Nov 18 10:46:59.384 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:46:59.539 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.18s
Nov 18 10:46:59.548 INFO [stderr]      Running /target/debug/deps/spanner1-08c0babb982a92db
Nov 18 10:46:59.558 INFO [stdout] 
Nov 18 10:46:59.558 INFO [stdout] running 0 tests
Nov 18 10:46:59.558 INFO [stdout] 
Nov 18 10:46:59.558 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 10:46:59.558 INFO [stdout] 
Nov 18 10:46:59.564 INFO [stderr] su: No module specific data is present
Nov 18 10:47:00.931 INFO running `"docker" "inspect" "8dd2ef442138b5f3a5d2ba7e86a37f88ac59aeadf90e067e3104ba2e240fadaf"`
Nov 18 10:47:01.175 INFO running `"docker" "rm" "-f" "8dd2ef442138b5f3a5d2ba7e86a37f88ac59aeadf90e067e3104ba2e240fadaf"`
Nov 18 10:47:01.463 INFO [stdout] 8dd2ef442138b5f3a5d2ba7e86a37f88ac59aeadf90e067e3104ba2e240fadaf