Aug 30 10:33:35.334 INFO checking mlnx-ofed-libibverbs-sys-0.0.6 against master#545f22340f72ee0efaf6463efb43a2840e3d35db for pr-53699 Aug 30 10:33:35.334 INFO running: cargo +545f22340f72ee0efaf6463efb43a2840e3d35db-alt check --frozen --all --all-targets Aug 30 10:33:35.334 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-2/pr-53699/master#545f22340f72ee0efaf6463efb43a2840e3d35db:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53699/worker-2/master#545f22340f72ee0efaf6463efb43a2840e3d35db:/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 +545f22340f72ee0efaf6463efb43a2840e3d35db-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Aug 30 10:33:35.498 INFO blam! 647d75081764a2ea8b49a4738ef76ffebc412989bd43acef328d49749e7f5975 Aug 30 10:33:35.499 INFO running `"docker" "start" "-a" "647d75081764a2ea8b49a4738ef76ffebc412989bd43acef328d49749e7f5975"` Aug 30 10:33:36.395 INFO kablam! Compiling mlnx-ofed-libibverbs-sys v0.0.6 (file:///source) Aug 30 10:33:37.399 INFO kablam! error: failed to run custom build command for `mlnx-ofed-libibverbs-sys v0.0.6 (file:///source)` Aug 30 10:33:37.399 INFO kablam! process didn't exit successfully: `/target/debug/build/mlnx-ofed-libibverbs-sys-1965a9d02b6a1863/build-script-build` (exit code: 101) Aug 30 10:33:37.399 INFO kablam! --- stderr Aug 30 10:33:37.399 INFO kablam! thread 'main' panicked at 'Command 'bindgen-wrapper/build-under-cargo' failed with exit code '1' (standard out was ''; standard error was 'compile-rdma-core:The binary 'x86_64-linux-musl-gcc' needs to be in the path Aug 30 10:33:37.399 INFO kablam! compile-rdma-core:The binary 'x86_64-linux-musl-ar' needs to be in the path Aug 30 10:33:37.399 INFO kablam! compile-rdma-core:FAIL:Please make sure that the missing binaries are installed because 'make' Aug 30 10:33:37.400 INFO kablam! ')', src/build.rs:44:2 Aug 30 10:33:37.400 INFO kablam! stack backtrace: Aug 30 10:33:37.400 INFO kablam! 0: 0x55dce7aaf7fe - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::hb14c0e50253b2613 Aug 30 10:33:37.400 INFO kablam! at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49 Aug 30 10:33:37.400 INFO kablam! 1: 0x55dce7aa1b36 - std::sys_common::backtrace::print::h6350b89a6173f177 Aug 30 10:33:37.400 INFO kablam! at libstd/sys_common/backtrace.rs:71 Aug 30 10:33:37.400 INFO kablam! at libstd/sys_common/backtrace.rs:59 Aug 30 10:33:37.400 INFO kablam! 2: 0x55dce7aa043d - std::panicking::default_hook::{{closure}}::h0d296196459c0d68 Aug 30 10:33:37.400 INFO kablam! at libstd/panicking.rs:211 Aug 30 10:33:37.400 INFO kablam! 3: 0x55dce7aa01b0 - std::panicking::default_hook::h3b75ddcdb4e292c2 Aug 30 10:33:37.400 INFO kablam! at libstd/panicking.rs:227 Aug 30 10:33:37.400 INFO kablam! 4: 0x55dce7aa09fc - std::panicking::rust_panic_with_hook::h78c3f66b7bf47c8e Aug 30 10:33:37.400 INFO kablam! at libstd/panicking.rs:476 Aug 30 10:33:37.400 INFO kablam! 5: 0x55dce7aa05f9 - std::panicking::continue_panic_fmt::h0dca0000433d53cd Aug 30 10:33:37.400 INFO kablam! at libstd/panicking.rs:390 Aug 30 10:33:37.400 INFO kablam! 6: 0x55dce7aa055d - std::panicking::begin_panic_fmt::h6675e33fa9a9ec2c Aug 30 10:33:37.400 INFO kablam! at libstd/panicking.rs:345 Aug 30 10:33:37.400 INFO kablam! 7: 0x55dce7a9c841 - build_script_build::panic_if_process_not_successul::haeb994b5e60ddf31 Aug 30 10:33:37.400 INFO kablam! at src/build.rs:44 Aug 30 10:33:37.401 INFO kablam! 8: 0x55dce7a9c2e7 - build_script_build::tool::h7de71ffbaf333162 Aug 30 10:33:37.401 INFO kablam! at src/build.rs:22 Aug 30 10:33:37.401 INFO kablam! 9: 0x55dce7a9bf2e - build_script_build::main::h27fcc200d7b95cda Aug 30 10:33:37.401 INFO kablam! at src/build.rs:16 Aug 30 10:33:37.401 INFO kablam! 10: 0x55dce7a9965f - std::rt::lang_start::{{closure}}::he35c73af4abfcc6d Aug 30 10:33:37.401 INFO kablam! at /checkout/src/libstd/rt.rs:74 Aug 30 10:33:37.401 INFO kablam! 11: 0x55dce7aa04e2 - std::panicking::try::do_call::heda1385a4d443830 Aug 30 10:33:37.401 INFO kablam! at libstd/rt.rs:59 Aug 30 10:33:37.401 INFO kablam! at libstd/panicking.rs:310 Aug 30 10:33:37.401 INFO kablam! 12: 0x55dce7ac1719 - __rust_maybe_catch_panic Aug 30 10:33:37.401 INFO kablam! at libpanic_unwind/lib.rs:102 Aug 30 10:33:37.401 INFO kablam! 13: 0x55dce7aab415 - std::rt::lang_start_internal::h92d079b55bc853f9 Aug 30 10:33:37.401 INFO kablam! at libstd/panicking.rs:289 Aug 30 10:33:37.401 INFO kablam! at libstd/panic.rs:392 Aug 30 10:33:37.401 INFO kablam! at libstd/rt.rs:58 Aug 30 10:33:37.401 INFO kablam! 14: 0x55dce7a99637 - std::rt::lang_start::h7a8d3e9a8a9e42a0 Aug 30 10:33:37.401 INFO kablam! at /checkout/src/libstd/rt.rs:74 Aug 30 10:33:37.401 INFO kablam! 15: 0x55dce7a9cb89 - main Aug 30 10:33:37.401 INFO kablam! 16: 0x7f7ad069082f - __libc_start_main Aug 30 10:33:37.401 INFO kablam! 17: 0x55dce7a96df8 - _start Aug 30 10:33:37.402 INFO kablam! 18: 0x0 - Aug 30 10:33:37.402 INFO kablam! Aug 30 10:33:37.403 INFO kablam! su: No module specific data is present Aug 30 10:33:37.813 INFO running `"docker" "rm" "-f" "647d75081764a2ea8b49a4738ef76ffebc412989bd43acef328d49749e7f5975"` Aug 30 10:33:37.920 INFO blam! 647d75081764a2ea8b49a4738ef76ffebc412989bd43acef328d49749e7f5975