Nov 18 02:54:30.293 INFO testing pyramid_grok-0.2.0 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982 Nov 18 02:54:30.295 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 02:54:30.499 INFO [stdout] 88f2f2b49fb5cfbf6735c42f125973c0be8e66a0ec4cf59d0ce3d9202283bcd5 Nov 18 02:54:30.501 INFO running `"docker" "start" "-a" "88f2f2b49fb5cfbf6735c42f125973c0be8e66a0ec4cf59d0ce3d9202283bcd5"` Nov 18 02:54:31.779 INFO [stderr] usermod: no changes Nov 18 02:54:31.831 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 02:54:31.832 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 02:54:31.833 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 02:54:31.834 INFO [stderr] files will be included as a binary target: Nov 18 02:54:31.834 INFO [stderr] Nov 18 02:54:31.834 INFO [stderr] * /source/src/main.rs Nov 18 02:54:31.835 INFO [stderr] Nov 18 02:54:31.836 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 02:54:31.836 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 02:54:31.836 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 02:54:31.837 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 02:54:31.837 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 02:54:31.837 INFO [stderr] Nov 18 02:54:31.838 INFO [stderr] For more information on this warning you can consult Nov 18 02:54:31.838 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 02:54:31.838 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`, Nov 18 02:54:31.839 INFO [stderr] please set bin.path in Cargo.toml Nov 18 02:54:31.925 INFO [stderr] Compiling term_size v0.2.3 Nov 18 02:54:31.925 INFO [stderr] Compiling png v0.8.0 Nov 18 02:54:32.323 INFO [stderr] Compiling clap v2.19.3 Nov 18 02:54:34.247 INFO [stderr] Compiling image v0.14.0 Nov 18 02:54:56.203 INFO [stderr] Compiling pyramid_grok v0.2.0 (/source) Nov 18 02:55:03.731 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 31.92s Nov 18 02:55:03.769 INFO [stderr] su: No module specific data is present Nov 18 02:55:04.838 INFO running `"docker" "inspect" "88f2f2b49fb5cfbf6735c42f125973c0be8e66a0ec4cf59d0ce3d9202283bcd5"` Nov 18 02:55:04.969 INFO running `"docker" "rm" "-f" "88f2f2b49fb5cfbf6735c42f125973c0be8e66a0ec4cf59d0ce3d9202283bcd5"` Nov 18 02:55:05.072 INFO [stdout] 88f2f2b49fb5cfbf6735c42f125973c0be8e66a0ec4cf59d0ce3d9202283bcd5 Nov 18 02:55:05.076 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 02:55:05.283 INFO [stdout] c36a7f71996df57a6faa95039e59af08e1899bc5bddb69346ad500e37fbae45b Nov 18 02:55:05.285 INFO running `"docker" "start" "-a" "c36a7f71996df57a6faa95039e59af08e1899bc5bddb69346ad500e37fbae45b"` Nov 18 02:55:05.830 INFO [stderr] usermod: no changes Nov 18 02:55:05.875 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 02:55:05.875 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 02:55:05.875 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 02:55:05.875 INFO [stderr] files will be included as a binary target: Nov 18 02:55:05.875 INFO [stderr] Nov 18 02:55:05.875 INFO [stderr] * /source/src/main.rs Nov 18 02:55:05.875 INFO [stderr] Nov 18 02:55:05.875 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 02:55:05.875 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 02:55:05.875 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 02:55:05.875 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 02:55:05.875 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 02:55:05.875 INFO [stderr] Nov 18 02:55:05.875 INFO [stderr] For more information on this warning you can consult Nov 18 02:55:05.875 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 02:55:05.875 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`, Nov 18 02:55:05.875 INFO [stderr] please set bin.path in Cargo.toml Nov 18 02:55:05.934 INFO [stderr] Compiling pyramid_grok v0.2.0 (/source) Nov 18 02:55:09.969 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 4.10s Nov 18 02:55:09.976 INFO [stderr] su: No module specific data is present Nov 18 02:55:11.541 INFO running `"docker" "inspect" "c36a7f71996df57a6faa95039e59af08e1899bc5bddb69346ad500e37fbae45b"` Nov 18 02:55:11.883 INFO running `"docker" "rm" "-f" "c36a7f71996df57a6faa95039e59af08e1899bc5bddb69346ad500e37fbae45b"` Nov 18 02:55:12.163 INFO [stdout] c36a7f71996df57a6faa95039e59af08e1899bc5bddb69346ad500e37fbae45b Nov 18 02:55:12.167 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 02:55:12.647 INFO [stdout] dd379eea8e8f1cdae773bc4ed43abc72c26be51c65eeef285fb07286a43b503d Nov 18 02:55:12.651 INFO running `"docker" "start" "-a" "dd379eea8e8f1cdae773bc4ed43abc72c26be51c65eeef285fb07286a43b503d"` Nov 18 02:55:14.835 INFO [stderr] usermod: no changes Nov 18 02:55:14.895 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 02:55:14.895 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 02:55:14.895 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 02:55:14.895 INFO [stderr] files will be included as a binary target: Nov 18 02:55:14.895 INFO [stderr] Nov 18 02:55:14.895 INFO [stderr] * /source/src/main.rs Nov 18 02:55:14.895 INFO [stderr] Nov 18 02:55:14.895 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 02:55:14.895 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 02:55:14.895 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 02:55:14.895 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 02:55:14.895 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 02:55:14.895 INFO [stderr] Nov 18 02:55:14.895 INFO [stderr] For more information on this warning you can consult Nov 18 02:55:14.895 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 02:55:14.895 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`, Nov 18 02:55:14.895 INFO [stderr] please set bin.path in Cargo.toml Nov 18 02:55:14.971 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.10s Nov 18 02:55:14.975 INFO [stderr] Running /target/debug/deps/pyramid_grok-d69464cc5c9fffbc Nov 18 02:55:14.979 INFO [stdout] Nov 18 02:55:14.979 INFO [stdout] running 0 tests Nov 18 02:55:14.979 INFO [stdout] Nov 18 02:55:14.979 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 18 02:55:14.979 INFO [stdout] Nov 18 02:55:14.979 INFO [stdout] Nov 18 02:55:14.979 INFO [stdout] running 0 tests Nov 18 02:55:14.979 INFO [stdout] Nov 18 02:55:14.979 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 18 02:55:14.979 INFO [stdout] Nov 18 02:55:14.979 INFO [stderr] Running /target/debug/deps/pyramid-b19b970f18420179 Nov 18 02:55:14.979 INFO [stderr] Doc-tests pyramid_grok Nov 18 02:55:18.869 INFO [stdout] Nov 18 02:55:18.869 INFO [stdout] running 0 tests Nov 18 02:55:18.869 INFO [stdout] Nov 18 02:55:18.869 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 18 02:55:18.869 INFO [stdout] Nov 18 02:55:18.879 INFO [stderr] su: No module specific data is present Nov 18 02:55:19.252 INFO running `"docker" "inspect" "dd379eea8e8f1cdae773bc4ed43abc72c26be51c65eeef285fb07286a43b503d"` Nov 18 02:55:19.417 INFO running `"docker" "rm" "-f" "dd379eea8e8f1cdae773bc4ed43abc72c26be51c65eeef285fb07286a43b503d"` Nov 18 02:55:19.553 INFO [stdout] dd379eea8e8f1cdae773bc4ed43abc72c26be51c65eeef285fb07286a43b503d