Sep 02 09:45:24.756 INFO checking judy-sys-0.0.2 against try#952c7dbfa2628309f557b367929ffc17af20b332 for pr-53851 Sep 02 09:45:24.756 INFO running: cargo +952c7dbfa2628309f557b367929ffc17af20b332-alt check --frozen --all --all-targets Sep 02 09:45:24.757 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-2/pr-53851/try#952c7dbfa2628309f557b367929ffc17af20b332:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53851/worker-2/try#952c7dbfa2628309f557b367929ffc17af20b332:/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 +952c7dbfa2628309f557b367929ffc17af20b332-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:24.996 INFO blam! 6e534786a68eef28c97086d7eb0042ac277d6e14ac7ba9e26681cdda04b1643f Sep 02 09:45:24.998 INFO running `"docker" "start" "-a" "6e534786a68eef28c97086d7eb0042ac277d6e14ac7ba9e26681cdda04b1643f"` Sep 02 09:45:25.768 INFO kablam! Compiling judy-sys v0.0.2 (file:///source) Sep 02 09:45:26.976 INFO kablam! error: failed to run custom build command for `judy-sys v0.0.2 (file:///source)` Sep 02 09:45:26.976 INFO kablam! process didn't exit successfully: `/target/debug/build/judy-sys-19fc510478002ca5/build-script-build` (exit code: 101) Sep 02 09:45:26.976 INFO kablam! --- stderr Sep 02 09:45:26.976 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:26.976 INFO kablam! compile-judy:The binary 'x86_64-linux-musl-gcc' needs to be in the path Sep 02 09:45:26.976 INFO kablam! compile-judy:The binary 'x86_64-linux-musl-ar' needs to be in the path Sep 02 09:45:26.976 INFO kablam! compile-judy:FAIL:Please make sure that the missing binaries are installed because 'make' Sep 02 09:45:26.976 INFO kablam! ')', src/build.rs:47:2 Sep 02 09:45:26.976 INFO kablam! stack backtrace: Sep 02 09:45:26.976 INFO kablam! 0: 0x55ef425c3cde - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h8608d381b52a1cc7 Sep 02 09:45:26.976 INFO kablam! at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49 Sep 02 09:45:26.976 INFO kablam! 1: 0x55ef425b77e6 - std::sys_common::backtrace::print::hf96fbb6301ca8111 Sep 02 09:45:26.976 INFO kablam! at libstd/sys_common/backtrace.rs:71 Sep 02 09:45:26.976 INFO kablam! at libstd/sys_common/backtrace.rs:59 Sep 02 09:45:26.976 INFO kablam! 2: 0x55ef425b60ed - std::panicking::default_hook::{{closure}}::h2e8fa0d6ce9ebecc Sep 02 09:45:26.976 INFO kablam! at libstd/panicking.rs:211 Sep 02 09:45:26.976 INFO kablam! 3: 0x55ef425b5e60 - std::panicking::default_hook::h3e385661c8d6b6f8 Sep 02 09:45:26.976 INFO kablam! at libstd/panicking.rs:227 Sep 02 09:45:26.976 INFO kablam! 4: 0x55ef425b66ac - std::panicking::rust_panic_with_hook::h82448672ce6401e7 Sep 02 09:45:26.976 INFO kablam! at libstd/panicking.rs:477 Sep 02 09:45:26.976 INFO kablam! 5: 0x55ef425b62a9 - std::panicking::continue_panic_fmt::h7abacf9371d614d8 Sep 02 09:45:26.977 INFO kablam! at libstd/panicking.rs:391 Sep 02 09:45:26.977 INFO kablam! 6: 0x55ef425b620d - std::panicking::begin_panic_fmt::h7b5ce7842a1f14ab Sep 02 09:45:26.977 INFO kablam! at libstd/panicking.rs:346 Sep 02 09:45:26.977 INFO kablam! 7: 0x55ef425b2541 - build_script_build::panicIfProcessNotSuccessful::h01fc3c99e9a6d9f3 Sep 02 09:45:26.977 INFO kablam! at src/build.rs:47 Sep 02 09:45:26.977 INFO kablam! 8: 0x55ef425b1fe7 - build_script_build::tool::h8b9abe70102d8c0f Sep 02 09:45:26.977 INFO kablam! at src/build.rs:25 Sep 02 09:45:26.977 INFO kablam! 9: 0x55ef425b1d04 - build_script_build::main::hc08d5d39a8768623 Sep 02 09:45:26.977 INFO kablam! at src/build.rs:19 Sep 02 09:45:26.977 INFO kablam! 10: 0x55ef425af42f - std::rt::lang_start::{{closure}}::h67b7b6c5a14e7bdb Sep 02 09:45:26.977 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 09:45:26.977 INFO kablam! 11: 0x55ef425b6192 - std::panicking::try::do_call::he8eb7284c711bc58 Sep 02 09:45:26.977 INFO kablam! at libstd/rt.rs:59 Sep 02 09:45:26.977 INFO kablam! at libstd/panicking.rs:310 Sep 02 09:45:26.977 INFO kablam! 12: 0x55ef425d5a39 - __rust_maybe_catch_panic Sep 02 09:45:26.977 INFO kablam! at libpanic_unwind/lib.rs:103 Sep 02 09:45:26.977 INFO kablam! 13: 0x55ef425c0765 - std::rt::lang_start_internal::h25421c11e0cff495 Sep 02 09:45:26.977 INFO kablam! at libstd/panicking.rs:289 Sep 02 09:45:26.977 INFO kablam! at libstd/panic.rs:392 Sep 02 09:45:26.977 INFO kablam! at libstd/rt.rs:58 Sep 02 09:45:26.977 INFO kablam! 14: 0x55ef425af407 - std::rt::lang_start::h17edcade0ccdcb74 Sep 02 09:45:26.977 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 09:45:26.977 INFO kablam! 15: 0x55ef425b2839 - main Sep 02 09:45:26.977 INFO kablam! 16: 0x7fe6e931b82f - __libc_start_main Sep 02 09:45:26.977 INFO kablam! 17: 0x55ef425acbc8 - _start Sep 02 09:45:26.978 INFO kablam! 18: 0x0 - Sep 02 09:45:26.978 INFO kablam! Sep 02 09:45:26.978 INFO kablam! su: No module specific data is present Sep 02 09:45:27.427 INFO running `"docker" "rm" "-f" "6e534786a68eef28c97086d7eb0042ac277d6e14ac7ba9e26681cdda04b1643f"` Sep 02 09:45:27.561 INFO blam! 6e534786a68eef28c97086d7eb0042ac277d6e14ac7ba9e26681cdda04b1643f