Dec 03 12:32:53.804 INFO testing evic-0.1.1 against 1.30.1 for beta-1.31-5
Dec 03 12:32:53.804 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-0/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/beta-1.31-5/1.30.1:/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.1 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"`
Dec 03 12:32:54.312 INFO [stdout] 96eac0e1f11baecf6097d0e4783adf2c9ccceda0f22f70843c66371a9cb76acd
Dec 03 12:32:54.314 INFO running `"docker" "start" "-a" "96eac0e1f11baecf6097d0e4783adf2c9ccceda0f22f70843c66371a9cb76acd"`
Dec 03 12:32:55.154 INFO [stderr] usermod: no changes
Dec 03 12:32:55.199 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 03 12:32:55.199 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 03 12:32:55.199 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 12:32:55.199 INFO [stderr] files will be included as a binary target:
Dec 03 12:32:55.199 INFO [stderr] 
Dec 03 12:32:55.199 INFO [stderr] * /source/src/main.rs
Dec 03 12:32:55.199 INFO [stderr] 
Dec 03 12:32:55.199 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 12:32:55.199 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 03 12:32:55.199 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 03 12:32:55.199 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 12:32:55.199 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 12:32:55.199 INFO [stderr] 
Dec 03 12:32:55.199 INFO [stderr] For more information on this warning you can consult
Dec 03 12:32:55.199 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 12:32:55.199 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `evicutil`,
Dec 03 12:32:55.199 INFO [stderr] please set bin.path in Cargo.toml
Dec 03 12:32:55.239 INFO [stderr]    Compiling evic v0.1.1 (/source)
Dec 03 12:32:57.932 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.74s
Dec 03 12:32:57.936 INFO [stderr] su: No module specific data is present
Dec 03 12:32:58.846 INFO running `"docker" "inspect" "96eac0e1f11baecf6097d0e4783adf2c9ccceda0f22f70843c66371a9cb76acd"`
Dec 03 12:32:59.219 INFO running `"docker" "rm" "-f" "96eac0e1f11baecf6097d0e4783adf2c9ccceda0f22f70843c66371a9cb76acd"`
Dec 03 12:32:59.495 INFO [stdout] 96eac0e1f11baecf6097d0e4783adf2c9ccceda0f22f70843c66371a9cb76acd
Dec 03 12:32:59.500 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-0/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/beta-1.31-5/1.30.1:/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.1 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"`
Dec 03 12:32:59.890 INFO [stdout] 664188b8457a97d541e289b8a574baa116f745806ece85dbc942eb4da2501de2
Dec 03 12:32:59.892 INFO running `"docker" "start" "-a" "664188b8457a97d541e289b8a574baa116f745806ece85dbc942eb4da2501de2"`
Dec 03 12:33:00.954 INFO [stderr] usermod: no changes
Dec 03 12:33:00.999 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 03 12:33:00.999 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 03 12:33:00.999 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 12:33:00.999 INFO [stderr] files will be included as a binary target:
Dec 03 12:33:00.999 INFO [stderr] 
Dec 03 12:33:00.999 INFO [stderr] * /source/src/main.rs
Dec 03 12:33:00.999 INFO [stderr] 
Dec 03 12:33:00.999 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 12:33:00.999 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 03 12:33:00.999 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 03 12:33:00.999 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 12:33:00.999 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 12:33:00.999 INFO [stderr] 
Dec 03 12:33:00.999 INFO [stderr] For more information on this warning you can consult
Dec 03 12:33:00.999 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 12:33:00.999 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `evicutil`,
Dec 03 12:33:00.999 INFO [stderr] please set bin.path in Cargo.toml
Dec 03 12:33:01.019 INFO [stderr]    Compiling evic v0.1.1 (/source)
Dec 03 12:33:03.051 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.07s
Dec 03 12:33:03.055 INFO [stderr] su: No module specific data is present
Dec 03 12:33:04.179 INFO running `"docker" "inspect" "664188b8457a97d541e289b8a574baa116f745806ece85dbc942eb4da2501de2"`
Dec 03 12:33:04.316 INFO running `"docker" "rm" "-f" "664188b8457a97d541e289b8a574baa116f745806ece85dbc942eb4da2501de2"`
Dec 03 12:33:04.426 INFO [stdout] 664188b8457a97d541e289b8a574baa116f745806ece85dbc942eb4da2501de2
Dec 03 12:33:04.428 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-0/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/beta-1.31-5/1.30.1:/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.1 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"`
Dec 03 12:33:04.634 INFO [stdout] bd9c1dd1464efccee2a4df817ad7597f675183f2b9a44bedf0209a57f0305551
Dec 03 12:33:04.636 INFO running `"docker" "start" "-a" "bd9c1dd1464efccee2a4df817ad7597f675183f2b9a44bedf0209a57f0305551"`
Dec 03 12:33:05.100 INFO [stderr] usermod: no changes
Dec 03 12:33:05.121 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 03 12:33:05.121 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 03 12:33:05.121 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 12:33:05.121 INFO [stderr] files will be included as a binary target:
Dec 03 12:33:05.121 INFO [stderr] 
Dec 03 12:33:05.121 INFO [stderr] * /source/src/main.rs
Dec 03 12:33:05.121 INFO [stderr] 
Dec 03 12:33:05.121 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 12:33:05.121 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 03 12:33:05.121 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 03 12:33:05.121 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 12:33:05.121 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 12:33:05.121 INFO [stderr] 
Dec 03 12:33:05.121 INFO [stderr] For more information on this warning you can consult
Dec 03 12:33:05.122 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 12:33:05.122 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `evicutil`,
Dec 03 12:33:05.122 INFO [stderr] please set bin.path in Cargo.toml
Dec 03 12:33:05.139 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
Dec 03 12:33:05.139 INFO [stdout] 
Dec 03 12:33:05.139 INFO [stderr]      Running /target/debug/deps/evic-cbf3194516017b00
Dec 03 12:33:05.139 INFO [stdout] running 2 tests
Dec 03 12:33:05.140 INFO [stdout] test firmware::tests::it_fails_when_firmware_size_exceeds_capacity ... ok
Dec 03 12:33:05.140 INFO [stdout] test firmware::tests::it_decrypts ... ok
Dec 03 12:33:05.140 INFO [stdout] 
Dec 03 12:33:05.140 INFO [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 12:33:05.140 INFO [stdout] 
Dec 03 12:33:05.141 INFO [stderr]      Running /target/debug/deps/evicutil-8a2f314f4fd65c37
Dec 03 12:33:05.143 INFO [stdout] 
Dec 03 12:33:05.143 INFO [stdout] running 2 tests
Dec 03 12:33:05.143 INFO [stdout] test tests::it_should_give_suffixed_output_path ... ok
Dec 03 12:33:05.143 INFO [stdout] test tests::it_should_give_suffixed_output_path_despite_no_extension ... ok
Dec 03 12:33:05.143 INFO [stdout] 
Dec 03 12:33:05.143 INFO [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 12:33:05.143 INFO [stdout] 
Dec 03 12:33:05.147 INFO [stderr]    Doc-tests evic
Dec 03 12:33:06.224 INFO [stdout] 
Dec 03 12:33:06.224 INFO [stdout] running 1 test
Dec 03 12:33:07.659 INFO [stdout] test src/firmware.rs - firmware::Firmware::decrypt (line 34) ... ok
Dec 03 12:33:07.659 INFO [stdout] 
Dec 03 12:33:07.659 INFO [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 12:33:07.659 INFO [stdout] 
Dec 03 12:33:07.675 INFO [stderr] su: No module specific data is present
Dec 03 12:33:08.052 INFO running `"docker" "inspect" "bd9c1dd1464efccee2a4df817ad7597f675183f2b9a44bedf0209a57f0305551"`
Dec 03 12:33:08.204 INFO running `"docker" "rm" "-f" "bd9c1dd1464efccee2a4df817ad7597f675183f2b9a44bedf0209a57f0305551"`
Dec 03 12:33:08.293 INFO [stdout] bd9c1dd1464efccee2a4df817ad7597f675183f2b9a44bedf0209a57f0305551
