Dec 15 00:38:00.667 INFO testing pyramid_grok-0.2.0 against try#aa49d8ef14939ddec0e34b346b60174a5673d48f for pr-56550 Dec 15 00:38:00.667 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-2/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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"` Dec 15 00:38:00.840 INFO [stdout] f46ba1b63432e6bae6ff545607f6253287a2d57a752adcd7522ebdbc170b56e6 Dec 15 00:38:00.844 INFO running `"docker" "start" "-a" "f46ba1b63432e6bae6ff545607f6253287a2d57a752adcd7522ebdbc170b56e6"` Dec 15 00:38:01.510 INFO [stderr] usermod: no changes Dec 15 00:38:01.611 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 15 00:38:01.611 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 15 00:38:01.611 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 15 00:38:01.611 INFO [stderr] files will be included as a binary target: Dec 15 00:38:01.611 INFO [stderr] Dec 15 00:38:01.611 INFO [stderr] * /source/src/main.rs Dec 15 00:38:01.611 INFO [stderr] Dec 15 00:38:01.611 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 15 00:38:01.611 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 15 00:38:01.611 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 15 00:38:01.611 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 15 00:38:01.611 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 15 00:38:01.611 INFO [stderr] Dec 15 00:38:01.611 INFO [stderr] For more information on this warning you can consult Dec 15 00:38:01.611 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 15 00:38:01.611 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`, Dec 15 00:38:01.611 INFO [stderr] please set bin.path in Cargo.toml Dec 15 00:38:01.728 INFO [stderr] Compiling clap v2.19.3 Dec 15 00:38:16.537 INFO [stderr] Compiling pyramid_grok v0.2.0 (/source) Dec 15 00:38:26.012 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 24.48s Dec 15 00:38:26.018 INFO [stderr] su: No module specific data is present Dec 15 00:38:27.210 INFO running `"docker" "inspect" "f46ba1b63432e6bae6ff545607f6253287a2d57a752adcd7522ebdbc170b56e6"` Dec 15 00:38:27.501 INFO running `"docker" "rm" "-f" "f46ba1b63432e6bae6ff545607f6253287a2d57a752adcd7522ebdbc170b56e6"` Dec 15 00:38:27.820 INFO [stdout] f46ba1b63432e6bae6ff545607f6253287a2d57a752adcd7522ebdbc170b56e6 Dec 15 00:38:27.825 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-2/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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"` Dec 15 00:38:28.331 INFO [stdout] e4aafd4ec9ac9303fec3f7180c7468aae3e52f915a0bae994b6cfac99f0903d0 Dec 15 00:38:28.334 INFO running `"docker" "start" "-a" "e4aafd4ec9ac9303fec3f7180c7468aae3e52f915a0bae994b6cfac99f0903d0"` Dec 15 00:38:30.176 INFO [stderr] usermod: no changes Dec 15 00:38:30.231 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 15 00:38:30.231 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 15 00:38:30.231 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 15 00:38:30.231 INFO [stderr] files will be included as a binary target: Dec 15 00:38:30.231 INFO [stderr] Dec 15 00:38:30.231 INFO [stderr] * /source/src/main.rs Dec 15 00:38:30.231 INFO [stderr] Dec 15 00:38:30.231 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 15 00:38:30.231 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 15 00:38:30.231 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 15 00:38:30.231 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 15 00:38:30.231 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 15 00:38:30.231 INFO [stderr] Dec 15 00:38:30.231 INFO [stderr] For more information on this warning you can consult Dec 15 00:38:30.231 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 15 00:38:30.231 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`, Dec 15 00:38:30.231 INFO [stderr] please set bin.path in Cargo.toml Dec 15 00:38:30.351 INFO [stderr] Compiling pyramid_grok v0.2.0 (/source) Dec 15 00:38:34.922 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 4.71s Dec 15 00:38:34.928 INFO [stderr] su: No module specific data is present Dec 15 00:38:35.732 INFO running `"docker" "inspect" "e4aafd4ec9ac9303fec3f7180c7468aae3e52f915a0bae994b6cfac99f0903d0"` Dec 15 00:38:36.021 INFO running `"docker" "rm" "-f" "e4aafd4ec9ac9303fec3f7180c7468aae3e52f915a0bae994b6cfac99f0903d0"` Dec 15 00:38:36.287 INFO [stdout] e4aafd4ec9ac9303fec3f7180c7468aae3e52f915a0bae994b6cfac99f0903d0 Dec 15 00:38:36.289 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-2/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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"` Dec 15 00:38:36.821 INFO [stdout] 50ccec77c5b0f0ea30b00551d07915dc589a1d964197f89820094fcf38c212ed Dec 15 00:38:36.823 INFO running `"docker" "start" "-a" "50ccec77c5b0f0ea30b00551d07915dc589a1d964197f89820094fcf38c212ed"` Dec 15 00:38:37.878 INFO [stderr] usermod: no changes Dec 15 00:38:37.936 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 15 00:38:37.936 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 15 00:38:37.936 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 15 00:38:37.936 INFO [stderr] files will be included as a binary target: Dec 15 00:38:37.936 INFO [stderr] Dec 15 00:38:37.936 INFO [stderr] * /source/src/main.rs Dec 15 00:38:37.936 INFO [stderr] Dec 15 00:38:37.936 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 15 00:38:37.936 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 15 00:38:37.936 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 15 00:38:37.936 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 15 00:38:37.936 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 15 00:38:37.936 INFO [stderr] Dec 15 00:38:37.936 INFO [stderr] For more information on this warning you can consult Dec 15 00:38:37.936 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 15 00:38:37.936 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`, Dec 15 00:38:37.936 INFO [stderr] please set bin.path in Cargo.toml Dec 15 00:38:38.016 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.10s Dec 15 00:38:38.031 INFO [stderr] Running /target/debug/deps/pyramid_grok-283c6c6aa536c34f Dec 15 00:38:38.035 INFO [stdout] Dec 15 00:38:38.035 INFO [stdout] running 0 tests Dec 15 00:38:38.035 INFO [stdout] Dec 15 00:38:38.035 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 15 00:38:38.035 INFO [stdout] Dec 15 00:38:38.039 INFO [stdout] Dec 15 00:38:38.039 INFO [stderr] Running /target/debug/deps/pyramid-2773b0716ea61473 Dec 15 00:38:38.039 INFO [stdout] running 0 tests Dec 15 00:38:38.039 INFO [stderr] Doc-tests pyramid_grok Dec 15 00:38:38.039 INFO [stdout] Dec 15 00:38:38.039 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 15 00:38:38.039 INFO [stdout] Dec 15 00:38:42.617 INFO [stdout] Dec 15 00:38:42.618 INFO [stdout] running 0 tests Dec 15 00:38:42.618 INFO [stdout] Dec 15 00:38:42.618 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 15 00:38:42.618 INFO [stdout] Dec 15 00:38:42.623 INFO [stderr] su: No module specific data is present Dec 15 00:38:43.583 INFO running `"docker" "inspect" "50ccec77c5b0f0ea30b00551d07915dc589a1d964197f89820094fcf38c212ed"` Dec 15 00:38:43.861 INFO running `"docker" "rm" "-f" "50ccec77c5b0f0ea30b00551d07915dc589a1d964197f89820094fcf38c212ed"` Dec 15 00:38:44.211 INFO [stdout] 50ccec77c5b0f0ea30b00551d07915dc589a1d964197f89820094fcf38c212ed