Sep 02 09:45:25.676 INFO checking judy-sys-0.0.2 against master#1114ab684fbad001c4e580326d8eb4d8c4e917d3 for pr-53851 Sep 02 09:45:25.676 INFO running: cargo +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets Sep 02 09:45:25.677 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-1/pr-53851/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53851/worker-1/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 02 09:45:25.865 INFO blam! 59b883014fc29669bd2a1b79665e5b3b1a002fd9aecfab830d82c7eeb37683f0 Sep 02 09:45:25.867 INFO running `"docker" "start" "-a" "59b883014fc29669bd2a1b79665e5b3b1a002fd9aecfab830d82c7eeb37683f0"` Sep 02 09:45:26.507 INFO kablam! Compiling judy-sys v0.0.2 (file:///source) Sep 02 09:45:27.604 INFO kablam! error: failed to run custom build command for `judy-sys v0.0.2 (file:///source)` Sep 02 09:45:27.604 INFO kablam! process didn't exit successfully: `/target/debug/build/judy-sys-8a92e06dec6450fd/build-script-build` (exit code: 101) Sep 02 09:45:27.604 INFO kablam! --- stderr Sep 02 09:45:27.604 INFO kablam! thread 'main' panicked at 'Command 'build-under-cargo' failed with exit code '1' (standard out was ''; standard error was 'build-under-cargo:Whilst this script is designed to be run under cargo, it can run independently. We're setting CARGO_MANIFEST_DIR to '/source' Sep 02 09:45:27.604 INFO kablam! compile-judy:The binary 'x86_64-linux-musl-gcc' needs to be in the path Sep 02 09:45:27.604 INFO kablam! compile-judy:The binary 'x86_64-linux-musl-ar' needs to be in the path Sep 02 09:45:27.604 INFO kablam! compile-judy:FAIL:Please make sure that the missing binaries are installed because 'make' Sep 02 09:45:27.604 INFO kablam! ')', src/build.rs:47:2 Sep 02 09:45:27.604 INFO kablam! stack backtrace: Sep 02 09:45:27.605 INFO kablam! 0: 0x55a2c58f6cde - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::ha200f2cd684ebd49 Sep 02 09:45:27.605 INFO kablam! at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49 Sep 02 09:45:27.605 INFO kablam! 1: 0x55a2c58ea7e6 - std::sys_common::backtrace::print::hfe3d4e47b4c8e48c Sep 02 09:45:27.605 INFO kablam! at libstd/sys_common/backtrace.rs:71 Sep 02 09:45:27.605 INFO kablam! at libstd/sys_common/backtrace.rs:59 Sep 02 09:45:27.605 INFO kablam! 2: 0x55a2c58e90ed - std::panicking::default_hook::{{closure}}::hf56af31102a42941 Sep 02 09:45:27.605 INFO kablam! at libstd/panicking.rs:211 Sep 02 09:45:27.605 INFO kablam! 3: 0x55a2c58e8e60 - std::panicking::default_hook::ha51b5d4eb7ec526d Sep 02 09:45:27.605 INFO kablam! at libstd/panicking.rs:227 Sep 02 09:45:27.605 INFO kablam! 4: 0x55a2c58e96ac - std::panicking::rust_panic_with_hook::hd585483f9daec810 Sep 02 09:45:27.605 INFO kablam! at libstd/panicking.rs:477 Sep 02 09:45:27.605 INFO kablam! 5: 0x55a2c58e92a9 - std::panicking::continue_panic_fmt::h918075cde557b461 Sep 02 09:45:27.605 INFO kablam! at libstd/panicking.rs:391 Sep 02 09:45:27.605 INFO kablam! 6: 0x55a2c58e920d - std::panicking::begin_panic_fmt::h5e5c6b72bacdc05a Sep 02 09:45:27.605 INFO kablam! at libstd/panicking.rs:346 Sep 02 09:45:27.605 INFO kablam! 7: 0x55a2c58e5541 - build_script_build::panicIfProcessNotSuccessful::h76f0c9e39cb65afd Sep 02 09:45:27.605 INFO kablam! at src/build.rs:47 Sep 02 09:45:27.605 INFO kablam! 8: 0x55a2c58e4fe7 - build_script_build::tool::h93ff82020fcbb6ce Sep 02 09:45:27.605 INFO kablam! at src/build.rs:25 Sep 02 09:45:27.605 INFO kablam! 9: 0x55a2c58e4d04 - build_script_build::main::h753cb5a5f2ba8cbe Sep 02 09:45:27.606 INFO kablam! at src/build.rs:19 Sep 02 09:45:27.606 INFO kablam! 10: 0x55a2c58e242f - std::rt::lang_start::{{closure}}::h8b86786851bf5fa8 Sep 02 09:45:27.606 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 09:45:27.606 INFO kablam! 11: 0x55a2c58e9192 - std::panicking::try::do_call::hea63f5620482e896 Sep 02 09:45:27.606 INFO kablam! at libstd/rt.rs:59 Sep 02 09:45:27.606 INFO kablam! at libstd/panicking.rs:310 Sep 02 09:45:27.606 INFO kablam! 12: 0x55a2c5908a39 - __rust_maybe_catch_panic Sep 02 09:45:27.606 INFO kablam! at libpanic_unwind/lib.rs:103 Sep 02 09:45:27.606 INFO kablam! 13: 0x55a2c58f3765 - std::rt::lang_start_internal::hfd6e69240f0360f8 Sep 02 09:45:27.606 INFO kablam! at libstd/panicking.rs:289 Sep 02 09:45:27.606 INFO kablam! at libstd/panic.rs:392 Sep 02 09:45:27.606 INFO kablam! at libstd/rt.rs:58 Sep 02 09:45:27.606 INFO kablam! 14: 0x55a2c58e2407 - std::rt::lang_start::h69ad0b5772d382c3 Sep 02 09:45:27.606 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 09:45:27.606 INFO kablam! 15: 0x55a2c58e5839 - main Sep 02 09:45:27.606 INFO kablam! 16: 0x7f68d317782f - __libc_start_main Sep 02 09:45:27.606 INFO kablam! 17: 0x55a2c58dfbc8 - _start Sep 02 09:45:27.606 INFO kablam! 18: 0x0 - Sep 02 09:45:27.606 INFO kablam! Sep 02 09:45:27.608 INFO kablam! su: No module specific data is present Sep 02 09:45:28.062 INFO running `"docker" "rm" "-f" "59b883014fc29669bd2a1b79665e5b3b1a002fd9aecfab830d82c7eeb37683f0"` Sep 02 09:45:28.190 INFO blam! 59b883014fc29669bd2a1b79665e5b3b1a002fd9aecfab830d82c7eeb37683f0