Nov 18 10:38:43.883 INFO testing google-tagmanager2-cli-1.0.7+20171108 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982 Nov 18 10:38:43.883 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 10:38:44.352 INFO [stdout] 8944c6821f152d28c338365d2de3eca9de3b469c2ca8b4908e126c787ce25e5d Nov 18 10:38:44.355 INFO running `"docker" "start" "-a" "8944c6821f152d28c338365d2de3eca9de3b469c2ca8b4908e126c787ce25e5d"` Nov 18 10:38:46.502 INFO [stderr] usermod: no changes Nov 18 10:38:46.567 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:38:46.567 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:38:46.567 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:38:46.567 INFO [stderr] files will be included as a binary target: Nov 18 10:38:46.567 INFO [stderr] Nov 18 10:38:46.567 INFO [stderr] * /source/src/main.rs Nov 18 10:38:46.567 INFO [stderr] Nov 18 10:38:46.567 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:38:46.567 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:38:46.567 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:38:46.567 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:38:46.567 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:38:46.567 INFO [stderr] Nov 18 10:38:46.567 INFO [stderr] For more information on this warning you can consult Nov 18 10:38:46.567 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:38:46.567 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `tagmanager2`, Nov 18 10:38:46.567 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:38:46.703 INFO [stderr] Compiling google-tagmanager2 v1.0.8+20171108 Nov 18 10:39:00.879 INFO [stderr] Compiling google-tagmanager2-cli v1.0.7+20171108 (/source) Nov 18 10:39:38.190 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 51.66s Nov 18 10:39:38.192 INFO [stderr] su: No module specific data is present Nov 18 10:39:39.319 INFO running `"docker" "inspect" "8944c6821f152d28c338365d2de3eca9de3b469c2ca8b4908e126c787ce25e5d"` Nov 18 10:39:39.661 INFO running `"docker" "rm" "-f" "8944c6821f152d28c338365d2de3eca9de3b469c2ca8b4908e126c787ce25e5d"` Nov 18 10:39:40.044 INFO [stdout] 8944c6821f152d28c338365d2de3eca9de3b469c2ca8b4908e126c787ce25e5d Nov 18 10:39:40.047 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 10:39:40.513 INFO [stdout] 7f3cd61cf7c55c0ac69a8f199511aa53dbb8f0c0c375ac35be701ee10b09b73a Nov 18 10:39:40.516 INFO running `"docker" "start" "-a" "7f3cd61cf7c55c0ac69a8f199511aa53dbb8f0c0c375ac35be701ee10b09b73a"` Nov 18 10:39:42.747 INFO [stderr] usermod: no changes Nov 18 10:39:42.787 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:39:42.787 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:39:42.787 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:39:42.787 INFO [stderr] files will be included as a binary target: Nov 18 10:39:42.787 INFO [stderr] Nov 18 10:39:42.787 INFO [stderr] * /source/src/main.rs Nov 18 10:39:42.787 INFO [stderr] Nov 18 10:39:42.787 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:39:42.787 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:39:42.787 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:39:42.787 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:39:42.787 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:39:42.787 INFO [stderr] Nov 18 10:39:42.787 INFO [stderr] For more information on this warning you can consult Nov 18 10:39:42.787 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:39:42.787 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `tagmanager2`, Nov 18 10:39:42.787 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:39:43.028 INFO [stderr] Compiling google-tagmanager2-cli v1.0.7+20171108 (/source) Nov 18 10:39:50.917 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 8.14s Nov 18 10:39:50.929 INFO [stderr] su: No module specific data is present Nov 18 10:39:52.322 INFO running `"docker" "inspect" "7f3cd61cf7c55c0ac69a8f199511aa53dbb8f0c0c375ac35be701ee10b09b73a"` Nov 18 10:39:52.609 INFO running `"docker" "rm" "-f" "7f3cd61cf7c55c0ac69a8f199511aa53dbb8f0c0c375ac35be701ee10b09b73a"` Nov 18 10:39:52.978 INFO [stdout] 7f3cd61cf7c55c0ac69a8f199511aa53dbb8f0c0c375ac35be701ee10b09b73a Nov 18 10:39:52.985 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 10:39:53.403 INFO [stdout] 2031571b3880318eb91d7e2ad5c069bc8ca0187397f2d7ecb98232536f0da729 Nov 18 10:39:53.405 INFO running `"docker" "start" "-a" "2031571b3880318eb91d7e2ad5c069bc8ca0187397f2d7ecb98232536f0da729"` Nov 18 10:39:55.595 INFO [stderr] usermod: no changes Nov 18 10:39:55.675 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:39:55.675 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:39:55.675 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:39:55.675 INFO [stderr] files will be included as a binary target: Nov 18 10:39:55.675 INFO [stderr] Nov 18 10:39:55.675 INFO [stderr] * /source/src/main.rs Nov 18 10:39:55.675 INFO [stderr] Nov 18 10:39:55.675 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:39:55.675 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:39:55.675 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:39:55.675 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:39:55.675 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:39:55.675 INFO [stderr] Nov 18 10:39:55.675 INFO [stderr] For more information on this warning you can consult Nov 18 10:39:55.675 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:39:55.675 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `tagmanager2`, Nov 18 10:39:55.675 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:39:55.915 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.28s Nov 18 10:39:55.923 INFO [stderr] Running /target/debug/deps/tagmanager2-87912aa442033f9f Nov 18 10:39:55.923 INFO [stdout] Nov 18 10:39:55.923 INFO [stdout] running 0 tests Nov 18 10:39:55.923 INFO [stdout] Nov 18 10:39:55.923 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 18 10:39:55.923 INFO [stdout] Nov 18 10:39:55.927 INFO [stderr] su: No module specific data is present Nov 18 10:39:56.949 INFO running `"docker" "inspect" "2031571b3880318eb91d7e2ad5c069bc8ca0187397f2d7ecb98232536f0da729"` Nov 18 10:39:57.355 INFO running `"docker" "rm" "-f" "2031571b3880318eb91d7e2ad5c069bc8ca0187397f2d7ecb98232536f0da729"` Nov 18 10:39:57.667 INFO [stdout] 2031571b3880318eb91d7e2ad5c069bc8ca0187397f2d7ecb98232536f0da729