[INFO] crate evic 0.1.1 is already in cache
[INFO] extracting crate evic 0.1.1 into work/ex/beta-1.37-6/sources/1.36.0/reg/evic/0.1.1
[INFO] extracting crate evic 0.1.1 into work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/evic/0.1.1
[INFO] validating manifest of evic-0.1.1 on toolchain 1.36.0
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of evic-0.1.1 on toolchain beta-2019-07-23
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing evic-0.1.1
[INFO] finished frobbing evic-0.1.1
[INFO] frobbed toml for evic-0.1.1 written to work/ex/beta-1.37-6/sources/1.36.0/reg/evic/0.1.1/Cargo.toml
[INFO] started frobbing evic-0.1.1
[INFO] finished frobbing evic-0.1.1
[INFO] frobbed toml for evic-0.1.1 written to work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/evic/0.1.1/Cargo.toml
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] [stderr]     Blocking waiting for file lock on package cache lock
[INFO] [stderr]     Blocking waiting for file lock on package cache lock
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] testing evic-0.1.1 against 1.36.0 for beta-1.37-6
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-5/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/evic/0.1.1:/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.36.0" "build" "--frozen"`
[INFO] [stdout] 3f6404c80c1d757d757c8b2e814b58bfa02f46a391739856eadb4fb17d4bf726
[INFO] running `"docker" "start" "-a" "3f6404c80c1d757d757c8b2e814b58bfa02f46a391739856eadb4fb17d4bf726"`
[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 `evicutil`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]    Compiling evic v0.1.1 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.97s
[INFO] running `"docker" "inspect" "3f6404c80c1d757d757c8b2e814b58bfa02f46a391739856eadb4fb17d4bf726"`
[INFO] running `"docker" "rm" "-f" "3f6404c80c1d757d757c8b2e814b58bfa02f46a391739856eadb4fb17d4bf726"`
[INFO] [stdout] 3f6404c80c1d757d757c8b2e814b58bfa02f46a391739856eadb4fb17d4bf726
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-5/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/evic/0.1.1:/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.36.0" "test" "--frozen" "--no-run"`
[INFO] [stdout] 6850f1ec9576b3f9d1f9d34d06d88842c52edd693a7ac8b1ccfff185cec52715
[INFO] running `"docker" "start" "-a" "6850f1ec9576b3f9d1f9d34d06d88842c52edd693a7ac8b1ccfff185cec52715"`
[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 `evicutil`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]    Compiling evic v0.1.1 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.24s
[INFO] running `"docker" "inspect" "6850f1ec9576b3f9d1f9d34d06d88842c52edd693a7ac8b1ccfff185cec52715"`
[INFO] running `"docker" "rm" "-f" "6850f1ec9576b3f9d1f9d34d06d88842c52edd693a7ac8b1ccfff185cec52715"`
[INFO] [stdout] 6850f1ec9576b3f9d1f9d34d06d88842c52edd693a7ac8b1ccfff185cec52715
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-5/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/evic/0.1.1:/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.36.0" "test" "--frozen"`
[INFO] [stdout] 5b4025e45de7d03b8f77dcdfb6b39c9a69b2e3a9b0a691d8054b5b4686838e44
[INFO] running `"docker" "start" "-a" "5b4025e45de7d03b8f77dcdfb6b39c9a69b2e3a9b0a691d8054b5b4686838e44"`
[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 `evicutil`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
[INFO] [stderr]      Running /opt/crater/target/debug/deps/evic-cf008b8c6a590f93
[INFO] [stdout] 
[INFO] [stdout] running 2 tests
[INFO] [stdout] test firmware::tests::it_decrypts ... ok
[INFO] [stdout] test firmware::tests::it_fails_when_firmware_size_exceeds_capacity ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] [stderr]      Running /opt/crater/target/debug/deps/evicutil-c49c8ae90e4ab6b8
[INFO] [stdout] 
[INFO] [stdout] running 2 tests
[INFO] [stdout] test tests::it_should_give_suffixed_output_path ... ok
[INFO] [stdout] test tests::it_should_give_suffixed_output_path_despite_no_extension ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests evic
[INFO] [stdout] 
[INFO] [stdout] running 1 test
[INFO] [stdout] test src/firmware.rs - firmware::Firmware::decrypt (line 34) ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] running `"docker" "inspect" "5b4025e45de7d03b8f77dcdfb6b39c9a69b2e3a9b0a691d8054b5b4686838e44"`
[INFO] running `"docker" "rm" "-f" "5b4025e45de7d03b8f77dcdfb6b39c9a69b2e3a9b0a691d8054b5b4686838e44"`
[INFO] [stdout] 5b4025e45de7d03b8f77dcdfb6b39c9a69b2e3a9b0a691d8054b5b4686838e44