[INFO] crate pyramid_grok 0.2.0 is already in cache
[INFO] extracting crate pyramid_grok 0.2.0 into work/ex/beta-1.38-1/sources/1.37.0/reg/pyramid_grok/0.2.0
[INFO] extracting crate pyramid_grok 0.2.0 into work/ex/beta-1.38-1/sources/beta-2019-08-13/reg/pyramid_grok/0.2.0
[INFO] validating manifest of pyramid_grok-0.2.0 on toolchain 1.37.0
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of pyramid_grok-0.2.0 on toolchain beta-2019-08-13
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing pyramid_grok-0.2.0
[INFO] finished frobbing pyramid_grok-0.2.0
[INFO] frobbed toml for pyramid_grok-0.2.0 written to work/ex/beta-1.38-1/sources/1.37.0/reg/pyramid_grok/0.2.0/Cargo.toml
[INFO] started frobbing pyramid_grok-0.2.0
[INFO] finished frobbing pyramid_grok-0.2.0
[INFO] frobbed toml for pyramid_grok-0.2.0 written to work/ex/beta-1.38-1/sources/beta-2019-08-13/reg/pyramid_grok/0.2.0/Cargo.toml
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] testing pyramid_grok-0.2.0 against 1.37.0 for beta-1.38-1
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-4/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/reg/pyramid_grok/0.2.0:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "build" "--frozen"`
[INFO] [stdout] 0e0b5b99d3f5cb5c0873202e1fddaffa24078382a357220483ea742bdcf815e8
[INFO] running `"docker" "start" "-a" "0e0b5b99d3f5cb5c0873202e1fddaffa24078382a357220483ea742bdcf815e8"`
[INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other binary targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a binary target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/src/main.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobins = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `pyramid`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]    Compiling inflate v0.2.0
[INFO] [stderr]    Compiling png v0.8.0
[INFO] [stderr]    Compiling image v0.14.0
[INFO] [stderr]    Compiling pyramid_grok v0.2.0 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 24.59s
[INFO] running `"docker" "inspect" "0e0b5b99d3f5cb5c0873202e1fddaffa24078382a357220483ea742bdcf815e8"`
[INFO] running `"docker" "rm" "-f" "0e0b5b99d3f5cb5c0873202e1fddaffa24078382a357220483ea742bdcf815e8"`
[INFO] [stdout] 0e0b5b99d3f5cb5c0873202e1fddaffa24078382a357220483ea742bdcf815e8
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-4/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/reg/pyramid_grok/0.2.0:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "test" "--frozen" "--no-run"`
[INFO] [stdout] cafc3efba2094cc0950a49119a064d4ca867710acdd32114ddf9aba7d59989fb
[INFO] running `"docker" "start" "-a" "cafc3efba2094cc0950a49119a064d4ca867710acdd32114ddf9aba7d59989fb"`
[INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other binary targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a binary target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/src/main.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobins = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `pyramid`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]    Compiling pyramid_grok v0.2.0 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.34s
[INFO] running `"docker" "inspect" "cafc3efba2094cc0950a49119a064d4ca867710acdd32114ddf9aba7d59989fb"`
[INFO] running `"docker" "rm" "-f" "cafc3efba2094cc0950a49119a064d4ca867710acdd32114ddf9aba7d59989fb"`
[INFO] [stdout] cafc3efba2094cc0950a49119a064d4ca867710acdd32114ddf9aba7d59989fb
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-4/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/reg/pyramid_grok/0.2.0:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "test" "--frozen"`
[INFO] [stdout] 9a5bb6afc0f670816ea5ceccf925e8dba8737f7f860983017ebf2da564737eed
[INFO] running `"docker" "start" "-a" "9a5bb6afc0f670816ea5ceccf925e8dba8737f7f860983017ebf2da564737eed"`
[INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other binary targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a binary target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/src/main.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobins = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `pyramid`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.09s
[INFO] [stderr]      Running /opt/crater/target/debug/deps/pyramid_grok-0d7f2c25d0b00483
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] [stderr]      Running /opt/crater/target/debug/deps/pyramid-77bbe183315b63dd
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests pyramid_grok
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] running `"docker" "inspect" "9a5bb6afc0f670816ea5ceccf925e8dba8737f7f860983017ebf2da564737eed"`
[INFO] running `"docker" "rm" "-f" "9a5bb6afc0f670816ea5ceccf925e8dba8737f7f860983017ebf2da564737eed"`
[INFO] [stdout] 9a5bb6afc0f670816ea5ceccf925e8dba8737f7f860983017ebf2da564737eed