Dec 07 17:18:00.115 INFO testing evic-0.1.1 against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514
Dec 07 17:18:00.115 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-0/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 17:18:00.577 INFO [stdout] e2cdc51a990442d58f887653502597b1b0dd69a07c827c32a9a8502622b24238
Dec 07 17:18:00.579 INFO running `"docker" "start" "-a" "e2cdc51a990442d58f887653502597b1b0dd69a07c827c32a9a8502622b24238"`
Dec 07 17:18:02.228 INFO [stderr] usermod: no changes
Dec 07 17:18:02.268 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 07 17:18:02.268 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 07 17:18:02.268 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 07 17:18:02.268 INFO [stderr] files will be included as a binary target:
Dec 07 17:18:02.268 INFO [stderr] 
Dec 07 17:18:02.268 INFO [stderr] * /source/src/main.rs
Dec 07 17:18:02.268 INFO [stderr] 
Dec 07 17:18:02.268 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 07 17:18:02.268 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 07 17:18:02.268 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 07 17:18:02.268 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 07 17:18:02.268 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 07 17:18:02.268 INFO [stderr] 
Dec 07 17:18:02.268 INFO [stderr] For more information on this warning you can consult
Dec 07 17:18:02.268 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 07 17:18:02.268 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `evicutil`,
Dec 07 17:18:02.268 INFO [stderr] please set bin.path in Cargo.toml
Dec 07 17:18:02.308 INFO [stderr]    Compiling evic v0.1.1 (/source)
Dec 07 17:18:04.425 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.17s
Dec 07 17:18:04.429 INFO [stderr] su: No module specific data is present
Dec 07 17:18:05.063 INFO running `"docker" "inspect" "e2cdc51a990442d58f887653502597b1b0dd69a07c827c32a9a8502622b24238"`
Dec 07 17:18:05.292 INFO running `"docker" "rm" "-f" "e2cdc51a990442d58f887653502597b1b0dd69a07c827c32a9a8502622b24238"`
Dec 07 17:18:05.548 INFO [stdout] e2cdc51a990442d58f887653502597b1b0dd69a07c827c32a9a8502622b24238
Dec 07 17:18:05.548 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-0/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 17:18:05.936 INFO [stdout] 4f8d860fa19e3b0d8b56248fdc093d1af41801e3f8ad056eaa3cb133f1520484
Dec 07 17:18:05.938 INFO running `"docker" "start" "-a" "4f8d860fa19e3b0d8b56248fdc093d1af41801e3f8ad056eaa3cb133f1520484"`
Dec 07 17:18:06.611 INFO [stderr] usermod: no changes
Dec 07 17:18:06.638 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 07 17:18:06.638 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 07 17:18:06.638 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 07 17:18:06.638 INFO [stderr] files will be included as a binary target:
Dec 07 17:18:06.638 INFO [stderr] 
Dec 07 17:18:06.638 INFO [stderr] * /source/src/main.rs
Dec 07 17:18:06.638 INFO [stderr] 
Dec 07 17:18:06.638 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 07 17:18:06.638 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 07 17:18:06.638 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 07 17:18:06.638 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 07 17:18:06.638 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 07 17:18:06.638 INFO [stderr] 
Dec 07 17:18:06.638 INFO [stderr] For more information on this warning you can consult
Dec 07 17:18:06.638 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 07 17:18:06.638 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `evicutil`,
Dec 07 17:18:06.638 INFO [stderr] please set bin.path in Cargo.toml
Dec 07 17:18:06.653 INFO [stderr]    Compiling evic v0.1.1 (/source)
Dec 07 17:18:07.627 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.00s
Dec 07 17:18:07.631 INFO [stderr] su: No module specific data is present
Dec 07 17:18:08.085 INFO running `"docker" "inspect" "4f8d860fa19e3b0d8b56248fdc093d1af41801e3f8ad056eaa3cb133f1520484"`
Dec 07 17:18:08.218 INFO running `"docker" "rm" "-f" "4f8d860fa19e3b0d8b56248fdc093d1af41801e3f8ad056eaa3cb133f1520484"`
Dec 07 17:18:08.340 INFO [stdout] 4f8d860fa19e3b0d8b56248fdc093d1af41801e3f8ad056eaa3cb133f1520484
Dec 07 17:18:08.346 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-0/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 17:18:08.624 INFO [stdout] ea9d4a7abf729ec5352884b0ec746e9bdf302389ce4aeed794dfd232e09f54e2
Dec 07 17:18:08.631 INFO running `"docker" "start" "-a" "ea9d4a7abf729ec5352884b0ec746e9bdf302389ce4aeed794dfd232e09f54e2"`
Dec 07 17:18:09.509 INFO [stderr] usermod: no changes
Dec 07 17:18:09.540 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 07 17:18:09.540 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 07 17:18:09.540 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 07 17:18:09.540 INFO [stderr] files will be included as a binary target:
Dec 07 17:18:09.540 INFO [stderr] 
Dec 07 17:18:09.540 INFO [stderr] * /source/src/main.rs
Dec 07 17:18:09.540 INFO [stderr] 
Dec 07 17:18:09.540 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 07 17:18:09.540 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 07 17:18:09.540 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 07 17:18:09.540 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 07 17:18:09.540 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 07 17:18:09.540 INFO [stderr] 
Dec 07 17:18:09.540 INFO [stderr] For more information on this warning you can consult
Dec 07 17:18:09.540 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 07 17:18:09.540 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `evicutil`,
Dec 07 17:18:09.540 INFO [stderr] please set bin.path in Cargo.toml
Dec 07 17:18:09.555 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
Dec 07 17:18:09.558 INFO [stderr]      Running /target/debug/deps/evic-e179417509211ddb
Dec 07 17:18:09.576 INFO [stdout] 
Dec 07 17:18:09.576 INFO [stdout] running 2 tests
Dec 07 17:18:09.576 INFO [stdout] test firmware::tests::it_decrypts ... ok
Dec 07 17:18:09.576 INFO [stdout] test firmware::tests::it_fails_when_firmware_size_exceeds_capacity ... ok
Dec 07 17:18:09.576 INFO [stdout] 
Dec 07 17:18:09.576 INFO [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 07 17:18:09.576 INFO [stdout] 
Dec 07 17:18:09.576 INFO [stderr]      Running /target/debug/deps/evicutil-d758691227b37169
Dec 07 17:18:09.577 INFO [stdout] 
Dec 07 17:18:09.577 INFO [stdout] running 2 tests
Dec 07 17:18:09.578 INFO [stdout] test tests::it_should_give_suffixed_output_path ... ok
Dec 07 17:18:09.578 INFO [stderr]    Doc-tests evic
Dec 07 17:18:09.578 INFO [stdout] test tests::it_should_give_suffixed_output_path_despite_no_extension ... ok
Dec 07 17:18:09.578 INFO [stdout] 
Dec 07 17:18:09.578 INFO [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 07 17:18:09.578 INFO [stdout] 
Dec 07 17:18:10.087 INFO [stdout] 
Dec 07 17:18:10.087 INFO [stdout] running 1 test
Dec 07 17:18:10.822 INFO [stdout] test src/firmware.rs - firmware::Firmware::decrypt (line 34) ... ok
Dec 07 17:18:10.822 INFO [stdout] 
Dec 07 17:18:10.822 INFO [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 07 17:18:10.822 INFO [stdout] 
Dec 07 17:18:10.830 INFO [stderr] su: No module specific data is present
Dec 07 17:18:11.208 INFO running `"docker" "inspect" "ea9d4a7abf729ec5352884b0ec746e9bdf302389ce4aeed794dfd232e09f54e2"`
Dec 07 17:18:11.370 INFO running `"docker" "rm" "-f" "ea9d4a7abf729ec5352884b0ec746e9bdf302389ce4aeed794dfd232e09f54e2"`
Dec 07 17:18:11.592 INFO [stdout] ea9d4a7abf729ec5352884b0ec746e9bdf302389ce4aeed794dfd232e09f54e2