Nov 02 21:08:08.898 INFO testing evic-0.1.1 against 1.30.0 for beta-1.31-1
Nov 02 21:08:08.899 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-3/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-1/1.30.0:/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 +1.30.0 build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 02 21:08:09.324 INFO blam! a8b161313d2ccf625763bd20709008222b6261233ede3e759c64d3ae2bc5acb9
Nov 02 21:08:09.333 INFO running `"docker" "start" "-a" "a8b161313d2ccf625763bd20709008222b6261233ede3e759c64d3ae2bc5acb9"`
Nov 02 21:08:10.642 INFO kablam! usermod: no changes
Nov 02 21:08:10.691 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 21:08:10.691 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 21:08:10.691 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 21:08:10.691 INFO kablam! files will be included as a binary target:
Nov 02 21:08:10.691 INFO kablam! 
Nov 02 21:08:10.691 INFO kablam! * /source/src/main.rs
Nov 02 21:08:10.691 INFO kablam! 
Nov 02 21:08:10.691 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 21:08:10.691 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 21:08:10.691 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 21:08:10.691 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 21:08:10.691 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 21:08:10.691 INFO kablam! 
Nov 02 21:08:10.691 INFO kablam! For more information on this warning you can consult
Nov 02 21:08:10.691 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 21:08:10.691 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `evicutil`,
Nov 02 21:08:10.691 INFO kablam! please set bin.path in Cargo.toml
Nov 02 21:08:10.715 INFO kablam!    Compiling evic v0.1.1 (/source)
Nov 02 21:08:13.645 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.97s
Nov 02 21:08:13.665 INFO kablam! su: No module specific data is present
Nov 02 21:08:14.812 INFO running `"docker" "rm" "-f" "a8b161313d2ccf625763bd20709008222b6261233ede3e759c64d3ae2bc5acb9"`
Nov 02 21:08:15.180 INFO blam! a8b161313d2ccf625763bd20709008222b6261233ede3e759c64d3ae2bc5acb9
Nov 02 21:08:15.191 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-3/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-1/1.30.0:/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 +1.30.0 test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 02 21:08:15.658 INFO blam! a9322a5549e474d0d69ad4d86e20cacbfd020cbde369542c20ef4950ec7051e4
Nov 02 21:08:15.667 INFO running `"docker" "start" "-a" "a9322a5549e474d0d69ad4d86e20cacbfd020cbde369542c20ef4950ec7051e4"`
Nov 02 21:08:16.883 INFO kablam! usermod: no changes
Nov 02 21:08:16.939 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 21:08:16.939 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 21:08:16.939 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 21:08:16.939 INFO kablam! files will be included as a binary target:
Nov 02 21:08:16.939 INFO kablam! 
Nov 02 21:08:16.939 INFO kablam! * /source/src/main.rs
Nov 02 21:08:16.939 INFO kablam! 
Nov 02 21:08:16.939 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 21:08:16.939 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 21:08:16.939 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 21:08:16.939 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 21:08:16.939 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 21:08:16.939 INFO kablam! 
Nov 02 21:08:16.939 INFO kablam! For more information on this warning you can consult
Nov 02 21:08:16.939 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 21:08:16.939 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `evicutil`,
Nov 02 21:08:16.939 INFO kablam! please set bin.path in Cargo.toml
Nov 02 21:08:16.967 INFO kablam!    Compiling evic v0.1.1 (/source)
Nov 02 21:08:19.673 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.76s
Nov 02 21:08:19.677 INFO kablam! su: No module specific data is present
Nov 02 21:08:20.364 INFO running `"docker" "rm" "-f" "a9322a5549e474d0d69ad4d86e20cacbfd020cbde369542c20ef4950ec7051e4"`
Nov 02 21:08:20.731 INFO blam! a9322a5549e474d0d69ad4d86e20cacbfd020cbde369542c20ef4950ec7051e4
Nov 02 21:08:20.744 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-3/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-1/1.30.0:/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 +1.30.0 test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 02 21:08:21.291 INFO blam! c43ad4d09ce75d08d762c827cbe0a41621554c3b1f467abe5eb768027707315c
Nov 02 21:08:21.291 INFO running `"docker" "start" "-a" "c43ad4d09ce75d08d762c827cbe0a41621554c3b1f467abe5eb768027707315c"`
Nov 02 21:08:21.990 INFO kablam! usermod: no changes
Nov 02 21:08:22.035 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 21:08:22.035 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 21:08:22.035 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 21:08:22.035 INFO kablam! files will be included as a binary target:
Nov 02 21:08:22.035 INFO kablam! 
Nov 02 21:08:22.035 INFO kablam! * /source/src/main.rs
Nov 02 21:08:22.035 INFO kablam! 
Nov 02 21:08:22.035 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 21:08:22.035 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 21:08:22.035 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 21:08:22.035 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 21:08:22.035 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 21:08:22.035 INFO kablam! 
Nov 02 21:08:22.035 INFO kablam! For more information on this warning you can consult
Nov 02 21:08:22.035 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 21:08:22.035 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `evicutil`,
Nov 02 21:08:22.035 INFO kablam! please set bin.path in Cargo.toml
Nov 02 21:08:22.060 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.04s
Nov 02 21:08:22.060 INFO kablam!      Running /target/debug/deps/evic-384ce3d02e80c19d
Nov 02 21:08:22.064 INFO blam! 
Nov 02 21:08:22.064 INFO blam! running 2 tests
Nov 02 21:08:22.079 INFO blam! test firmware::tests::it_decrypts ... ok
Nov 02 21:08:22.079 INFO kablam!      Running /target/debug/deps/evicutil-3ea2b1a62a338fec
Nov 02 21:08:22.079 INFO blam! test firmware::tests::it_fails_when_firmware_size_exceeds_capacity ... ok
Nov 02 21:08:22.079 INFO kablam!    Doc-tests evic
Nov 02 21:08:22.079 INFO blam! 
Nov 02 21:08:22.079 INFO blam! test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 21:08:22.079 INFO blam! 
Nov 02 21:08:22.079 INFO blam! 
Nov 02 21:08:22.079 INFO blam! running 2 tests
Nov 02 21:08:22.079 INFO blam! test tests::it_should_give_suffixed_output_path ... ok
Nov 02 21:08:22.079 INFO blam! test tests::it_should_give_suffixed_output_path_despite_no_extension ... ok
Nov 02 21:08:22.079 INFO blam! 
Nov 02 21:08:22.079 INFO blam! test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 21:08:22.079 INFO blam! 
Nov 02 21:08:23.174 INFO blam! 
Nov 02 21:08:23.174 INFO blam! running 1 test
Nov 02 21:08:24.736 INFO blam! test src/firmware.rs - firmware::Firmware::decrypt (line 34) ... ok
Nov 02 21:08:24.737 INFO blam! 
Nov 02 21:08:24.737 INFO blam! test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 21:08:24.737 INFO blam! 
Nov 02 21:08:24.755 INFO kablam! su: No module specific data is present
Nov 02 21:08:25.249 INFO running `"docker" "rm" "-f" "c43ad4d09ce75d08d762c827cbe0a41621554c3b1f467abe5eb768027707315c"`
Nov 02 21:08:25.387 INFO blam! c43ad4d09ce75d08d762c827cbe0a41621554c3b1f467abe5eb768027707315c
