Sep 04 17:35:01.446 INFO checking hazel-0.0.1 against master#2687112ea6a8701cbf36e6dd4d77d64694cf93d8 for pr-53913 Sep 04 17:35:01.446 INFO running: cargo +2687112ea6a8701cbf36e6dd4d77d64694cf93d8-alt check --frozen --all --all-targets Sep 04 17:35:01.446 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-2/pr-53913/master#2687112ea6a8701cbf36e6dd4d77d64694cf93d8:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53913/worker-2/master#2687112ea6a8701cbf36e6dd4d77d64694cf93d8:/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 +2687112ea6a8701cbf36e6dd4d77d64694cf93d8-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Sep 04 17:35:01.638 INFO blam! 25314ee8f5267dcecc281c1bcc0a02454561f38d780e703f7934f299860ae31d Sep 04 17:35:01.640 INFO running `"docker" "start" "-a" "25314ee8f5267dcecc281c1bcc0a02454561f38d780e703f7934f299860ae31d"` Sep 04 17:35:02.398 INFO kablam! Checking bitboard v0.1.1 Sep 04 17:35:02.847 INFO kablam! error[E0432]: unresolved import `std::heap` Sep 04 17:35:02.848 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/bitboard-0.1.1/src/lib.rs:18:10 Sep 04 17:35:02.848 INFO kablam! | Sep 04 17:35:02.848 INFO kablam! 18 | use std::heap::{Alloc, Layout, Heap}; Sep 04 17:35:02.848 INFO kablam! | ^^^^ Could not find `heap` in `std` Sep 04 17:35:02.848 INFO kablam! Sep 04 17:35:03.068 INFO kablam! error: aborting due to previous error Sep 04 17:35:03.068 INFO kablam! Sep 04 17:35:03.068 INFO kablam! For more information about this error, try `rustc --explain E0432`. Sep 04 17:35:03.077 INFO kablam! error: Could not compile `bitboard`. Sep 04 17:35:03.077 INFO kablam! Sep 04 17:35:03.077 INFO kablam! To learn more, run the command again with --verbose. Sep 04 17:35:03.079 INFO kablam! su: No module specific data is present Sep 04 17:35:03.530 INFO running `"docker" "rm" "-f" "25314ee8f5267dcecc281c1bcc0a02454561f38d780e703f7934f299860ae31d"` Sep 04 17:35:03.618 INFO blam! 25314ee8f5267dcecc281c1bcc0a02454561f38d780e703f7934f299860ae31d