Nov 18 02:54:30.409 INFO testing pyramid_grok-0.2.0 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 18 02:54:30.409 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 02:54:30.551 INFO [stdout] 9c6d086e0eabc6b1dd2615e0d509c27ece83f7afef3fe4a25c374a2133b1a94a
Nov 18 02:54:30.554 INFO running `"docker" "start" "-a" "9c6d086e0eabc6b1dd2615e0d509c27ece83f7afef3fe4a25c374a2133b1a94a"`
Nov 18 02:54:31.734 INFO [stderr] usermod: no changes
Nov 18 02:54:31.783 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 02:54:31.783 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 02:54:31.784 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 02:54:31.784 INFO [stderr] files will be included as a binary target:
Nov 18 02:54:31.784 INFO [stderr] 
Nov 18 02:54:31.785 INFO [stderr] * /source/src/main.rs
Nov 18 02:54:31.785 INFO [stderr] 
Nov 18 02:54:31.785 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 02:54:31.786 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 02:54:31.786 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 02:54:31.786 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 02:54:31.787 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 02:54:31.787 INFO [stderr] 
Nov 18 02:54:31.787 INFO [stderr] For more information on this warning you can consult
Nov 18 02:54:31.787 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 02:54:31.788 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`,
Nov 18 02:54:31.788 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 02:54:31.920 INFO [stderr]    Compiling png v0.8.0
Nov 18 02:54:33.847 INFO [stderr]    Compiling image v0.14.0
Nov 18 02:54:48.011 INFO [stderr]    Compiling pyramid_grok v0.2.0 (/source)
Nov 18 02:54:55.909 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 24.15s
Nov 18 02:54:55.917 INFO [stderr] su: No module specific data is present
Nov 18 02:54:57.514 INFO running `"docker" "inspect" "9c6d086e0eabc6b1dd2615e0d509c27ece83f7afef3fe4a25c374a2133b1a94a"`
Nov 18 02:54:57.953 INFO running `"docker" "rm" "-f" "9c6d086e0eabc6b1dd2615e0d509c27ece83f7afef3fe4a25c374a2133b1a94a"`
Nov 18 02:54:58.335 INFO [stdout] 9c6d086e0eabc6b1dd2615e0d509c27ece83f7afef3fe4a25c374a2133b1a94a
Nov 18 02:54:58.339 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 02:54:58.813 INFO [stdout] 0a60c13569419fecdcef7b7d76fd3faf5d29be45edf8fdf9ded45a114f058e8f
Nov 18 02:54:58.816 INFO running `"docker" "start" "-a" "0a60c13569419fecdcef7b7d76fd3faf5d29be45edf8fdf9ded45a114f058e8f"`
Nov 18 02:55:01.223 INFO [stderr] usermod: no changes
Nov 18 02:55:01.327 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 02:55:01.327 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 02:55:01.327 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 02:55:01.327 INFO [stderr] files will be included as a binary target:
Nov 18 02:55:01.327 INFO [stderr] 
Nov 18 02:55:01.327 INFO [stderr] * /source/src/main.rs
Nov 18 02:55:01.327 INFO [stderr] 
Nov 18 02:55:01.327 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 02:55:01.327 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 02:55:01.327 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 02:55:01.327 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 02:55:01.327 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 02:55:01.327 INFO [stderr] 
Nov 18 02:55:01.327 INFO [stderr] For more information on this warning you can consult
Nov 18 02:55:01.327 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 02:55:01.327 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`,
Nov 18 02:55:01.327 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 02:55:01.431 INFO [stderr]    Compiling pyramid_grok v0.2.0 (/source)
Nov 18 02:55:05.001 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.73s
Nov 18 02:55:05.008 INFO [stderr] su: No module specific data is present
Nov 18 02:55:05.312 INFO running `"docker" "inspect" "0a60c13569419fecdcef7b7d76fd3faf5d29be45edf8fdf9ded45a114f058e8f"`
Nov 18 02:55:05.465 INFO running `"docker" "rm" "-f" "0a60c13569419fecdcef7b7d76fd3faf5d29be45edf8fdf9ded45a114f058e8f"`
Nov 18 02:55:05.615 INFO [stdout] 0a60c13569419fecdcef7b7d76fd3faf5d29be45edf8fdf9ded45a114f058e8f
Nov 18 02:55:05.617 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 02:55:05.794 INFO [stdout] 041c8a1c3f50aeac36bc4f9ba3623ecba2d5df34f339b8694dd39bf8d6fb4113
Nov 18 02:55:05.794 INFO running `"docker" "start" "-a" "041c8a1c3f50aeac36bc4f9ba3623ecba2d5df34f339b8694dd39bf8d6fb4113"`
Nov 18 02:55:07.509 INFO [stderr] usermod: no changes
Nov 18 02:55:07.551 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 02:55:07.551 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 02:55:07.551 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 02:55:07.551 INFO [stderr] files will be included as a binary target:
Nov 18 02:55:07.551 INFO [stderr] 
Nov 18 02:55:07.551 INFO [stderr] * /source/src/main.rs
Nov 18 02:55:07.551 INFO [stderr] 
Nov 18 02:55:07.551 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 02:55:07.551 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 02:55:07.551 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 02:55:07.551 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 02:55:07.551 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 02:55:07.551 INFO [stderr] 
Nov 18 02:55:07.551 INFO [stderr] For more information on this warning you can consult
Nov 18 02:55:07.551 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 02:55:07.551 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`,
Nov 18 02:55:07.551 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 02:55:07.677 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.14s
Nov 18 02:55:07.690 INFO [stderr]      Running /target/debug/deps/pyramid_grok-9b8944eb83db7ec6
Nov 18 02:55:07.694 INFO [stdout] 
Nov 18 02:55:07.694 INFO [stdout] running 0 tests
Nov 18 02:55:07.694 INFO [stdout] 
Nov 18 02:55:07.694 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 02:55:07.694 INFO [stdout] 
Nov 18 02:55:07.695 INFO [stderr]      Running /target/debug/deps/pyramid-70a1fbdf1b5d2ab4
Nov 18 02:55:07.700 INFO [stdout] 
Nov 18 02:55:07.700 INFO [stdout] running 0 tests
Nov 18 02:55:07.700 INFO [stdout] 
Nov 18 02:55:07.700 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 02:55:07.700 INFO [stdout] 
Nov 18 02:55:07.700 INFO [stderr]    Doc-tests pyramid_grok
Nov 18 02:55:11.567 INFO [stdout] 
Nov 18 02:55:11.567 INFO [stdout] running 0 tests
Nov 18 02:55:11.567 INFO [stdout] 
Nov 18 02:55:11.567 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 02:55:11.567 INFO [stdout] 
Nov 18 02:55:11.567 INFO [stderr] su: No module specific data is present
Nov 18 02:55:12.439 INFO running `"docker" "inspect" "041c8a1c3f50aeac36bc4f9ba3623ecba2d5df34f339b8694dd39bf8d6fb4113"`
Nov 18 02:55:12.717 INFO running `"docker" "rm" "-f" "041c8a1c3f50aeac36bc4f9ba3623ecba2d5df34f339b8694dd39bf8d6fb4113"`
Nov 18 02:55:13.007 INFO [stdout] 041c8a1c3f50aeac36bc4f9ba3623ecba2d5df34f339b8694dd39bf8d6fb4113