Dec 07 03:29:41.601 INFO testing pyramid_grok-0.2.0 against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514 Dec 07 03:29:41.601 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-6/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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 07 03:29:42.026 INFO [stdout] e422bda15bcce0a29bd3dd093c57379fd5aa92dc923e8a00195d3f90a78c98b5 Dec 07 03:29:42.028 INFO running `"docker" "start" "-a" "e422bda15bcce0a29bd3dd093c57379fd5aa92dc923e8a00195d3f90a78c98b5"` Dec 07 03:29:43.240 INFO [stderr] usermod: no changes Dec 07 03:29:43.300 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 07 03:29:43.300 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 07 03:29:43.300 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 07 03:29:43.300 INFO [stderr] files will be included as a binary target: Dec 07 03:29:43.300 INFO [stderr] Dec 07 03:29:43.300 INFO [stderr] * /source/src/main.rs Dec 07 03:29:43.300 INFO [stderr] Dec 07 03:29:43.300 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 07 03:29:43.300 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 07 03:29:43.300 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 07 03:29:43.300 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 07 03:29:43.300 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 07 03:29:43.300 INFO [stderr] Dec 07 03:29:43.300 INFO [stderr] For more information on this warning you can consult Dec 07 03:29:43.300 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 07 03:29:43.300 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`, Dec 07 03:29:43.300 INFO [stderr] please set bin.path in Cargo.toml Dec 07 03:29:43.436 INFO [stderr] Compiling png v0.8.0 Dec 07 03:29:45.717 INFO [stderr] Compiling image v0.14.0 Dec 07 03:30:02.891 INFO [stderr] Compiling pyramid_grok v0.2.0 (/source) Dec 07 03:30:11.824 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 28.57s Dec 07 03:30:11.828 INFO [stderr] su: No module specific data is present Dec 07 03:30:12.939 INFO running `"docker" "inspect" "e422bda15bcce0a29bd3dd093c57379fd5aa92dc923e8a00195d3f90a78c98b5"` Dec 07 03:30:13.198 INFO running `"docker" "rm" "-f" "e422bda15bcce0a29bd3dd093c57379fd5aa92dc923e8a00195d3f90a78c98b5"` Dec 07 03:30:13.360 INFO [stdout] e422bda15bcce0a29bd3dd093c57379fd5aa92dc923e8a00195d3f90a78c98b5 Dec 07 03:30:13.362 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-6/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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 07 03:30:13.632 INFO [stdout] 904593b18402808a50cd4af0be477ec59fb01c4b88fb3957207dccbe19ffc7ef Dec 07 03:30:13.638 INFO running `"docker" "start" "-a" "904593b18402808a50cd4af0be477ec59fb01c4b88fb3957207dccbe19ffc7ef"` Dec 07 03:30:14.284 INFO [stderr] usermod: no changes Dec 07 03:30:14.338 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 07 03:30:14.338 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 07 03:30:14.338 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 07 03:30:14.338 INFO [stderr] files will be included as a binary target: Dec 07 03:30:14.338 INFO [stderr] Dec 07 03:30:14.338 INFO [stderr] * /source/src/main.rs Dec 07 03:30:14.338 INFO [stderr] Dec 07 03:30:14.338 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 07 03:30:14.338 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 07 03:30:14.338 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 07 03:30:14.338 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 07 03:30:14.338 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 07 03:30:14.338 INFO [stderr] Dec 07 03:30:14.338 INFO [stderr] For more information on this warning you can consult Dec 07 03:30:14.338 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 07 03:30:14.338 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`, Dec 07 03:30:14.338 INFO [stderr] please set bin.path in Cargo.toml Dec 07 03:30:14.395 INFO [stderr] Compiling pyramid_grok v0.2.0 (/source) Dec 07 03:30:18.872 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 4.56s Dec 07 03:30:18.879 INFO [stderr] su: No module specific data is present Dec 07 03:30:19.743 INFO running `"docker" "inspect" "904593b18402808a50cd4af0be477ec59fb01c4b88fb3957207dccbe19ffc7ef"` Dec 07 03:30:19.988 INFO running `"docker" "rm" "-f" "904593b18402808a50cd4af0be477ec59fb01c4b88fb3957207dccbe19ffc7ef"` Dec 07 03:30:20.223 INFO [stdout] 904593b18402808a50cd4af0be477ec59fb01c4b88fb3957207dccbe19ffc7ef Dec 07 03:30:20.226 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-6/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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 07 03:30:20.508 INFO [stdout] e942d1376741257fbe3592012ae1d2f6482dcb6ced6ecd36b39571fda3d358c3 Dec 07 03:30:20.510 INFO running `"docker" "start" "-a" "e942d1376741257fbe3592012ae1d2f6482dcb6ced6ecd36b39571fda3d358c3"` Dec 07 03:30:20.952 INFO [stderr] usermod: no changes Dec 07 03:30:20.976 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 07 03:30:20.976 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 07 03:30:20.976 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 07 03:30:20.976 INFO [stderr] files will be included as a binary target: Dec 07 03:30:20.976 INFO [stderr] Dec 07 03:30:20.976 INFO [stderr] * /source/src/main.rs Dec 07 03:30:20.976 INFO [stderr] Dec 07 03:30:20.976 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 07 03:30:20.976 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 07 03:30:20.976 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 07 03:30:20.976 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 07 03:30:20.976 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 07 03:30:20.976 INFO [stderr] Dec 07 03:30:20.976 INFO [stderr] For more information on this warning you can consult Dec 07 03:30:20.976 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 07 03:30:20.976 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `pyramid`, Dec 07 03:30:20.976 INFO [stderr] please set bin.path in Cargo.toml Dec 07 03:30:21.018 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.05s Dec 07 03:30:21.030 INFO [stderr] Running /target/debug/deps/pyramid_grok-35ab9985f4e5a22f Dec 07 03:30:21.032 INFO [stdout] Dec 07 03:30:21.032 INFO [stdout] running 0 tests Dec 07 03:30:21.032 INFO [stdout] Dec 07 03:30:21.032 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 07 03:30:21.032 INFO [stdout] Dec 07 03:30:21.032 INFO [stderr] Running /target/debug/deps/pyramid-37b93a2fc465f2e5 Dec 07 03:30:21.037 INFO [stdout] Dec 07 03:30:21.037 INFO [stdout] running 0 tests Dec 07 03:30:21.037 INFO [stdout] Dec 07 03:30:21.037 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 07 03:30:21.037 INFO [stdout] Dec 07 03:30:21.038 INFO [stderr] Doc-tests pyramid_grok Dec 07 03:30:25.560 INFO [stdout] Dec 07 03:30:25.560 INFO [stdout] running 0 tests Dec 07 03:30:25.560 INFO [stdout] Dec 07 03:30:25.560 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 07 03:30:25.560 INFO [stdout] Dec 07 03:30:25.574 INFO [stderr] su: No module specific data is present Dec 07 03:30:26.192 INFO running `"docker" "inspect" "e942d1376741257fbe3592012ae1d2f6482dcb6ced6ecd36b39571fda3d358c3"` Dec 07 03:30:26.435 INFO running `"docker" "rm" "-f" "e942d1376741257fbe3592012ae1d2f6482dcb6ced6ecd36b39571fda3d358c3"` Dec 07 03:30:26.680 INFO [stdout] e942d1376741257fbe3592012ae1d2f6482dcb6ced6ecd36b39571fda3d358c3