Nov 29 04:54:17.388 INFO checking aes-ctr-0.3.0 against master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5 for pr-56074
Nov 29 04:54:17.388 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56074/worker-1/master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-56074/master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5:/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 +0b9f19dff1347e29bf4362ab5a8fab84b43023b5-alt check --frozen --all --all-targets" "-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"`
Nov 29 04:54:17.664 INFO [stdout] 1ce673adf8d7335d50bb8cc5923b090b9ddd99aca99c18188f21d4bc0c376ba8
Nov 29 04:54:17.666 INFO running `"docker" "start" "-a" "1ce673adf8d7335d50bb8cc5923b090b9ddd99aca99c18188f21d4bc0c376ba8"`
Nov 29 04:54:18.360 INFO [stderr] usermod: no changes
Nov 29 04:54:18.456 INFO [stderr]     Checking blobby v0.1.1
Nov 29 04:54:18.597 INFO [stderr]     Checking stream-cipher v0.3.0
Nov 29 04:54:18.850 INFO [stderr]     Checking ctr v0.3.0
Nov 29 04:54:19.320 INFO [stderr]     Checking aes-ctr v0.3.0 (/source)
Nov 29 04:54:22.696 INFO [stderr] error: cannot find macro `vec!` in this scope
Nov 29 04:54:22.696 INFO [stderr]  --> benches/aes192_ctr.rs:7:1
Nov 29 04:54:22.696 INFO [stderr]   |
Nov 29 04:54:22.696 INFO [stderr] 7 | bench_sync!(aes_ctr::Aes192Ctr);
Nov 29 04:54:22.696 INFO [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 04:54:22.724 INFO [stderr]   |
Nov 29 04:54:22.724 INFO [stderr]   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Nov 29 04:54:22.724 INFO [stderr] 
Nov 29 04:54:22.856 INFO [stderr] error[E0412]: cannot find type `Vec` in this scope
Nov 29 04:54:22.856 INFO [stderr]  --> benches/aes192_ctr.rs:7:1
Nov 29 04:54:22.856 INFO [stderr]   |
Nov 29 04:54:22.856 INFO [stderr] 7 | bench_sync!(aes_ctr::Aes192Ctr);
Nov 29 04:54:22.856 INFO [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
Nov 29 04:54:22.856 INFO [stderr]   |
Nov 29 04:54:22.856 INFO [stderr]   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Nov 29 04:54:22.856 INFO [stderr] 
Nov 29 04:54:22.856 INFO [stderr] error: aborting due to 2 previous errors
Nov 29 04:54:22.856 INFO [stderr] 
Nov 29 04:54:22.856 INFO [stderr] For more information about this error, try `rustc --explain E0412`.
Nov 29 04:54:22.876 INFO [stderr] error: Could not compile `aes-ctr`.
Nov 29 04:54:22.876 INFO [stderr] warning: build failed, waiting for other jobs to finish...
Nov 29 04:54:23.056 INFO [stderr] error: cannot find macro `vec!` in this scope
Nov 29 04:54:23.056 INFO [stderr]  --> benches/aes256_ctr.rs:7:1
Nov 29 04:54:23.056 INFO [stderr]   |
Nov 29 04:54:23.056 INFO [stderr] 7 | bench_sync!(aes_ctr::Aes128Ctr);
Nov 29 04:54:23.056 INFO [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 04:54:23.056 INFO [stderr]   |
Nov 29 04:54:23.056 INFO [stderr]   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Nov 29 04:54:23.056 INFO [stderr] 
Nov 29 04:54:23.140 INFO [stderr] error[E0412]: cannot find type `Vec` in this scope
Nov 29 04:54:23.140 INFO [stderr]  --> benches/aes256_ctr.rs:7:1
Nov 29 04:54:23.140 INFO [stderr]   |
Nov 29 04:54:23.140 INFO [stderr] 7 | bench_sync!(aes_ctr::Aes128Ctr);
Nov 29 04:54:23.140 INFO [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
Nov 29 04:54:23.140 INFO [stderr]   |
Nov 29 04:54:23.140 INFO [stderr]   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Nov 29 04:54:23.140 INFO [stderr] 
Nov 29 04:54:23.140 INFO [stderr] error: aborting due to 2 previous errors
Nov 29 04:54:23.140 INFO [stderr] 
Nov 29 04:54:23.140 INFO [stderr] For more information about this error, try `rustc --explain E0412`.
Nov 29 04:54:23.160 INFO [stderr] error: Could not compile `aes-ctr`.
Nov 29 04:54:23.160 INFO [stderr] warning: build failed, waiting for other jobs to finish...
Nov 29 04:54:23.472 INFO [stderr] error: cannot find macro `vec!` in this scope
Nov 29 04:54:23.472 INFO [stderr]  --> benches/aes128_ctr.rs:7:1
Nov 29 04:54:23.472 INFO [stderr]   |
Nov 29 04:54:23.472 INFO [stderr] 7 | bench_sync!(aes_ctr::Aes128Ctr);
Nov 29 04:54:23.472 INFO [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 04:54:23.472 INFO [stderr]   |
Nov 29 04:54:23.472 INFO [stderr]   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Nov 29 04:54:23.472 INFO [stderr] 
Nov 29 04:54:23.513 INFO [stderr] error[E0412]: cannot find type `Vec` in this scope
Nov 29 04:54:23.513 INFO [stderr]  --> benches/aes128_ctr.rs:7:1
Nov 29 04:54:23.513 INFO [stderr]   |
Nov 29 04:54:23.513 INFO [stderr] 7 | bench_sync!(aes_ctr::Aes128Ctr);
Nov 29 04:54:23.513 INFO [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
Nov 29 04:54:23.513 INFO [stderr]   |
Nov 29 04:54:23.513 INFO [stderr]   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
Nov 29 04:54:23.513 INFO [stderr] 
Nov 29 04:54:23.513 INFO [stderr] error: aborting due to 2 previous errors
Nov 29 04:54:23.513 INFO [stderr] 
Nov 29 04:54:23.513 INFO [stderr] For more information about this error, try `rustc --explain E0412`.
Nov 29 04:54:23.524 INFO [stderr] error: Could not compile `aes-ctr`.
Nov 29 04:54:23.524 INFO [stderr] 
Nov 29 04:54:23.524 INFO [stderr] To learn more, run the command again with --verbose.
Nov 29 04:54:23.528 INFO [stderr] su: No module specific data is present
Nov 29 04:54:24.205 INFO running `"docker" "inspect" "1ce673adf8d7335d50bb8cc5923b090b9ddd99aca99c18188f21d4bc0c376ba8"`
Nov 29 04:54:24.522 INFO running `"docker" "rm" "-f" "1ce673adf8d7335d50bb8cc5923b090b9ddd99aca99c18188f21d4bc0c376ba8"`
Nov 29 04:54:24.731 INFO [stdout] 1ce673adf8d7335d50bb8cc5923b090b9ddd99aca99c18188f21d4bc0c376ba8