Sep 04 13:07:05.076 INFO checking judy-sys-0.0.2 against try#6b43b862fabb13a0ce2a5371ea1e77ee1674b7e0 for pr-53893 Sep 04 13:07:05.076 INFO running: cargo +6b43b862fabb13a0ce2a5371ea1e77ee1674b7e0-alt check --frozen --all --all-targets Sep 04 13:07:05.076 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-3/pr-53893/try#6b43b862fabb13a0ce2a5371ea1e77ee1674b7e0:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53893/worker-3/try#6b43b862fabb13a0ce2a5371ea1e77ee1674b7e0:/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 +6b43b862fabb13a0ce2a5371ea1e77ee1674b7e0-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Sep 04 13:07:05.251 INFO blam! d48ee5074dc5c8f6b37a92a66439dd7a3322279bed1c0eea43d00bd032374134 Sep 04 13:07:05.252 INFO running `"docker" "start" "-a" "d48ee5074dc5c8f6b37a92a66439dd7a3322279bed1c0eea43d00bd032374134"` Sep 04 13:07:05.875 INFO kablam! Compiling judy-sys v0.0.2 (file:///source) Sep 04 13:07:06.866 INFO kablam! error: failed to run custom build command for `judy-sys v0.0.2 (file:///source)` Sep 04 13:07:06.867 INFO kablam! process didn't exit successfully: `/target/debug/build/judy-sys-b128c6c183acf476/build-script-build` (exit code: 101) Sep 04 13:07:06.867 INFO kablam! --- stderr Sep 04 13:07:06.867 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 04 13:07:06.867 INFO kablam! compile-judy:The binary 'x86_64-linux-musl-gcc' needs to be in the path Sep 04 13:07:06.867 INFO kablam! compile-judy:The binary 'x86_64-linux-musl-ar' needs to be in the path Sep 04 13:07:06.867 INFO kablam! compile-judy:FAIL:Please make sure that the missing binaries are installed because 'make' Sep 04 13:07:06.867 INFO kablam! ')', src/build.rs:47:2 Sep 04 13:07:06.867 INFO kablam! stack backtrace: Sep 04 13:07:06.867 INFO kablam! 0: 0x5586e13a5b5e - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::ha53509682dbd7f85 Sep 04 13:07:06.867 INFO kablam! at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49 Sep 04 13:07:06.867 INFO kablam! 1: 0x5586e1399796 - std::sys_common::backtrace::print::h3aced1bbe2b8ca94 Sep 04 13:07:06.867 INFO kablam! at libstd/sys_common/backtrace.rs:71 Sep 04 13:07:06.867 INFO kablam! at libstd/sys_common/backtrace.rs:59 Sep 04 13:07:06.867 INFO kablam! 2: 0x5586e13980cd - std::panicking::default_hook::{{closure}}::h76b1883c3c87e0fa Sep 04 13:07:06.867 INFO kablam! at libstd/panicking.rs:211 Sep 04 13:07:06.867 INFO kablam! 3: 0x5586e1397e40 - std::panicking::default_hook::h74b87988c51c021c Sep 04 13:07:06.867 INFO kablam! at libstd/panicking.rs:227 Sep 04 13:07:06.867 INFO kablam! 4: 0x5586e139868c - std::panicking::rust_panic_with_hook::h3878be5cebe1ecc9 Sep 04 13:07:06.867 INFO kablam! at libstd/panicking.rs:477 Sep 04 13:07:06.867 INFO kablam! 5: 0x5586e1398289 - std::panicking::continue_panic_fmt::h7964842efee54f94 Sep 04 13:07:06.867 INFO kablam! at libstd/panicking.rs:391 Sep 04 13:07:06.867 INFO kablam! 6: 0x5586e13981ed - std::panicking::begin_panic_fmt::h24162616eac839a2 Sep 04 13:07:06.867 INFO kablam! at libstd/panicking.rs:346 Sep 04 13:07:06.867 INFO kablam! 7: 0x5586e139454b - build_script_build::panicIfProcessNotSuccessful::hf10ab0cb38827509 Sep 04 13:07:06.867 INFO kablam! at src/build.rs:47 Sep 04 13:07:06.867 INFO kablam! 8: 0x5586e1394005 - build_script_build::tool::h9d17f8282fbc2edc Sep 04 13:07:06.867 INFO kablam! at src/build.rs:25 Sep 04 13:07:06.867 INFO kablam! 9: 0x5586e1393d32 - build_script_build::main::hd61a037af7bf8e7c Sep 04 13:07:06.867 INFO kablam! at src/build.rs:19 Sep 04 13:07:06.867 INFO kablam! 10: 0x5586e139145f - std::rt::lang_start::{{closure}}::h820b192121e1f47e Sep 04 13:07:06.867 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 04 13:07:06.867 INFO kablam! 11: 0x5586e1398172 - std::panicking::try::do_call::h2434b76b61552c7b Sep 04 13:07:06.867 INFO kablam! at libstd/rt.rs:59 Sep 04 13:07:06.867 INFO kablam! at libstd/panicking.rs:310 Sep 04 13:07:06.867 INFO kablam! 12: 0x5586e13b7c09 - __rust_maybe_catch_panic Sep 04 13:07:06.867 INFO kablam! at libpanic_unwind/lib.rs:103 Sep 04 13:07:06.867 INFO kablam! 13: 0x5586e13a25d5 - std::rt::lang_start_internal::h60780ef6735385b7 Sep 04 13:07:06.867 INFO kablam! at libstd/panicking.rs:289 Sep 04 13:07:06.867 INFO kablam! at libstd/panic.rs:392 Sep 04 13:07:06.867 INFO kablam! at libstd/rt.rs:58 Sep 04 13:07:06.867 INFO kablam! 14: 0x5586e1391437 - std::rt::lang_start::hffe145e31cad9411 Sep 04 13:07:06.867 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 04 13:07:06.867 INFO kablam! 15: 0x5586e1394839 - main Sep 04 13:07:06.867 INFO kablam! 16: 0x7f6b73f3582f - __libc_start_main Sep 04 13:07:06.867 INFO kablam! 17: 0x5586e138ebf8 - _start Sep 04 13:07:06.867 INFO kablam! 18: 0x0 - Sep 04 13:07:06.867 INFO kablam! Sep 04 13:07:06.869 INFO kablam! su: No module specific data is present Sep 04 13:07:07.299 INFO running `"docker" "rm" "-f" "d48ee5074dc5c8f6b37a92a66439dd7a3322279bed1c0eea43d00bd032374134"` Sep 04 13:07:07.394 INFO blam! d48ee5074dc5c8f6b37a92a66439dd7a3322279bed1c0eea43d00bd032374134