Nov 18 11:05:40.951 INFO testing google-identitytoolkit3-cli-1.0.7+20171122 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982 Nov 18 11:05:40.953 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 11:05:41.345 INFO [stdout] e53b4090ffc663c63e84174484a8d43bbac048c2b5eaabc22ba5c173f9659e77 Nov 18 11:05:41.345 INFO running `"docker" "start" "-a" "e53b4090ffc663c63e84174484a8d43bbac048c2b5eaabc22ba5c173f9659e77"` Nov 18 11:05:42.826 INFO [stderr] usermod: no changes Nov 18 11:05:42.883 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 11:05:42.883 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 11:05:42.883 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 11:05:42.883 INFO [stderr] files will be included as a binary target: Nov 18 11:05:42.883 INFO [stderr] Nov 18 11:05:42.883 INFO [stderr] * /source/src/main.rs Nov 18 11:05:42.883 INFO [stderr] Nov 18 11:05:42.883 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 11:05:42.883 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 11:05:42.883 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 11:05:42.883 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 11:05:42.883 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 11:05:42.883 INFO [stderr] Nov 18 11:05:42.883 INFO [stderr] For more information on this warning you can consult Nov 18 11:05:42.883 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 11:05:42.883 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `identitytoolkit3`, Nov 18 11:05:42.883 INFO [stderr] please set bin.path in Cargo.toml Nov 18 11:05:43.079 INFO [stderr] Compiling google-identitytoolkit3 v1.0.8+20180723 Nov 18 11:05:54.030 INFO [stderr] Compiling google-identitytoolkit3-cli v1.0.7+20171122 (/source) Nov 18 11:06:14.528 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 31.68s Nov 18 11:06:14.541 INFO [stderr] su: No module specific data is present Nov 18 11:06:15.300 INFO running `"docker" "inspect" "e53b4090ffc663c63e84174484a8d43bbac048c2b5eaabc22ba5c173f9659e77"` Nov 18 11:06:15.525 INFO running `"docker" "rm" "-f" "e53b4090ffc663c63e84174484a8d43bbac048c2b5eaabc22ba5c173f9659e77"` Nov 18 11:06:15.794 INFO [stdout] e53b4090ffc663c63e84174484a8d43bbac048c2b5eaabc22ba5c173f9659e77 Nov 18 11:06:15.798 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 11:06:16.263 INFO [stdout] 188a5f4dace0e5ee665227b67f85cc76e57c8fe71e8d9027e05193e0fa258efd Nov 18 11:06:16.266 INFO running `"docker" "start" "-a" "188a5f4dace0e5ee665227b67f85cc76e57c8fe71e8d9027e05193e0fa258efd"` Nov 18 11:06:18.111 INFO [stderr] usermod: no changes Nov 18 11:06:18.191 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 11:06:18.191 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 11:06:18.191 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 11:06:18.191 INFO [stderr] files will be included as a binary target: Nov 18 11:06:18.191 INFO [stderr] Nov 18 11:06:18.191 INFO [stderr] * /source/src/main.rs Nov 18 11:06:18.191 INFO [stderr] Nov 18 11:06:18.191 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 11:06:18.191 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 11:06:18.191 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 11:06:18.191 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 11:06:18.191 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 11:06:18.191 INFO [stderr] Nov 18 11:06:18.191 INFO [stderr] For more information on this warning you can consult Nov 18 11:06:18.191 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 11:06:18.191 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `identitytoolkit3`, Nov 18 11:06:18.191 INFO [stderr] please set bin.path in Cargo.toml Nov 18 11:06:18.404 INFO [stderr] Compiling google-identitytoolkit3-cli v1.0.7+20171122 (/source) Nov 18 11:06:24.275 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 6.12s Nov 18 11:06:24.278 INFO [stderr] su: No module specific data is present Nov 18 11:06:25.111 INFO running `"docker" "inspect" "188a5f4dace0e5ee665227b67f85cc76e57c8fe71e8d9027e05193e0fa258efd"` Nov 18 11:06:25.443 INFO running `"docker" "rm" "-f" "188a5f4dace0e5ee665227b67f85cc76e57c8fe71e8d9027e05193e0fa258efd"` Nov 18 11:06:25.823 INFO [stdout] 188a5f4dace0e5ee665227b67f85cc76e57c8fe71e8d9027e05193e0fa258efd Nov 18 11:06:25.833 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 11:06:26.251 INFO [stdout] a12b55e0cd1af12200bbb46681a8fc3d45f0301a040e077b054339df3d6afddd Nov 18 11:06:26.254 INFO running `"docker" "start" "-a" "a12b55e0cd1af12200bbb46681a8fc3d45f0301a040e077b054339df3d6afddd"` Nov 18 11:06:28.383 INFO [stderr] usermod: no changes Nov 18 11:06:28.427 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 11:06:28.427 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 11:06:28.427 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 11:06:28.427 INFO [stderr] files will be included as a binary target: Nov 18 11:06:28.427 INFO [stderr] Nov 18 11:06:28.427 INFO [stderr] * /source/src/main.rs Nov 18 11:06:28.427 INFO [stderr] Nov 18 11:06:28.427 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 11:06:28.427 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 11:06:28.427 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 11:06:28.427 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 11:06:28.427 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 11:06:28.427 INFO [stderr] Nov 18 11:06:28.427 INFO [stderr] For more information on this warning you can consult Nov 18 11:06:28.427 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 11:06:28.427 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `identitytoolkit3`, Nov 18 11:06:28.427 INFO [stderr] please set bin.path in Cargo.toml Nov 18 11:06:28.610 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.20s Nov 18 11:06:28.626 INFO [stderr] Running /target/debug/deps/identitytoolkit3-ad69aed5e05565dd Nov 18 11:06:28.629 INFO [stdout] Nov 18 11:06:28.629 INFO [stdout] running 0 tests Nov 18 11:06:28.629 INFO [stdout] Nov 18 11:06:28.629 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 18 11:06:28.629 INFO [stdout] Nov 18 11:06:28.635 INFO [stderr] su: No module specific data is present Nov 18 11:06:29.671 INFO running `"docker" "inspect" "a12b55e0cd1af12200bbb46681a8fc3d45f0301a040e077b054339df3d6afddd"` Nov 18 11:06:29.943 INFO running `"docker" "rm" "-f" "a12b55e0cd1af12200bbb46681a8fc3d45f0301a040e077b054339df3d6afddd"` Nov 18 11:06:30.407 INFO [stdout] a12b55e0cd1af12200bbb46681a8fc3d45f0301a040e077b054339df3d6afddd