Sep 01 17:45:29.673 INFO checking hazel-0.0.1 against master#1114ab684fbad001c4e580326d8eb4d8c4e917d3 for pr-53831 Sep 01 17:45:29.673 INFO running: cargo +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets Sep 01 17:45:29.674 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-2/pr-53831/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53831/worker-2/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/target:rw,Z" "-v" "/home/ec2-user/crater/./work/local/cargo-home:/cargo-home:ro,Z" "-v" "/home/ec2-user/crater/./work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=500" "-e" "CMD=cargo +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Sep 01 17:45:29.854 INFO blam! b6665a4d211e155c4f164a1b32a99ce890642d6ca85ff164e096278e96e0d206 Sep 01 17:45:29.857 INFO running `"docker" "start" "-a" "b6665a4d211e155c4f164a1b32a99ce890642d6ca85ff164e096278e96e0d206"` Sep 01 17:45:30.661 INFO kablam! Checking bitboard v0.1.1 Sep 01 17:45:31.298 INFO kablam! error[E0432]: unresolved import `std::heap` Sep 01 17:45:31.298 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/bitboard-0.1.1/src/lib.rs:18:10 Sep 01 17:45:31.298 INFO kablam! | Sep 01 17:45:31.298 INFO kablam! 18 | use std::heap::{Alloc, Layout, Heap}; Sep 01 17:45:31.298 INFO kablam! | ^^^^ Could not find `heap` in `std` Sep 01 17:45:31.298 INFO kablam! Sep 01 17:45:31.588 INFO kablam! error: aborting due to previous error Sep 01 17:45:31.588 INFO kablam! Sep 01 17:45:31.588 INFO kablam! For more information about this error, try `rustc --explain E0432`. Sep 01 17:45:31.598 INFO kablam! error: Could not compile `bitboard`. Sep 01 17:45:31.598 INFO kablam! Sep 01 17:45:31.598 INFO kablam! To learn more, run the command again with --verbose. Sep 01 17:45:31.600 INFO kablam! su: No module specific data is present Sep 01 17:45:32.224 INFO running `"docker" "rm" "-f" "b6665a4d211e155c4f164a1b32a99ce890642d6ca85ff164e096278e96e0d206"` Sep 01 17:45:32.388 INFO blam! b6665a4d211e155c4f164a1b32a99ce890642d6ca85ff164e096278e96e0d206