[INFO] crate libnuma-sys 0.0.9 is already in cache [INFO] extracting crate libnuma-sys 0.0.9 into work/ex/beta-1.37-6/sources/1.36.0/reg/libnuma-sys/0.0.9 [INFO] extracting crate libnuma-sys 0.0.9 into work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/libnuma-sys/0.0.9 [INFO] validating manifest of libnuma-sys-0.0.9 on toolchain 1.36.0 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] validating manifest of libnuma-sys-0.0.9 on toolchain beta-2019-07-23 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started frobbing libnuma-sys-0.0.9 [INFO] finished frobbing libnuma-sys-0.0.9 [INFO] frobbed toml for libnuma-sys-0.0.9 written to work/ex/beta-1.37-6/sources/1.36.0/reg/libnuma-sys/0.0.9/Cargo.toml [INFO] started frobbing libnuma-sys-0.0.9 [INFO] finished frobbing libnuma-sys-0.0.9 [INFO] frobbed toml for libnuma-sys-0.0.9 written to work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/libnuma-sys/0.0.9/Cargo.toml [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] testing libnuma-sys-0.0.9 against 1.36.0 for beta-1.37-6 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-3/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/libnuma-sys/0.0.9:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.36.0" "build" "--frozen"` [INFO] [stdout] 80d4ef1c8e192e7d3ff576be358c403f5b7030f2f713d3388e1719119d0c250b [INFO] running `"docker" "start" "-a" "80d4ef1c8e192e7d3ff576be358c403f5b7030f2f713d3388e1719119d0c250b"` [INFO] [stderr] Compiling libnuma-sys v0.0.9 (/opt/crater/workdir) [INFO] [stderr] error: failed to run custom build command for `libnuma-sys v0.0.9 (/opt/crater/workdir)` [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `/opt/crater/target/debug/build/libnuma-sys-a4b4969d908be068/build-script-build` (exit code: 101) [INFO] [stderr] --- stderr [INFO] [stderr] 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 [INFO] [stderr] compile-rdma-core:The binary 'x86_64-linux-musl-ar' needs to be in the path [INFO] [stderr] compile-rdma-core:FAIL:Please make sure that the missing binaries are installed because 'make' [INFO] [stderr] ')', src/build.rs:44:2 [INFO] [stderr] stack backtrace: [INFO] [stderr] 0: 0x5635c1064e13 - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h6485381528590a55 [INFO] [stderr] at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:39 [INFO] [stderr] 1: 0x5635c10609cb - std::sys_common::backtrace::_print::h49a82ae9552e35c7 [INFO] [stderr] at src/libstd/sys_common/backtrace.rs:71 [INFO] [stderr] 2: 0x5635c1063c26 - std::panicking::default_hook::{{closure}}::he20974adbefcc046 [INFO] [stderr] at src/libstd/sys_common/backtrace.rs:59 [INFO] [stderr] at src/libstd/panicking.rs:197 [INFO] [stderr] 3: 0x5635c10639b9 - std::panicking::default_hook::he4af6af4ac7fef7b [INFO] [stderr] at src/libstd/panicking.rs:211 [INFO] [stderr] 4: 0x5635c106427f - std::panicking::rust_panic_with_hook::h057ff03eb4c8000f [INFO] [stderr] at src/libstd/panicking.rs:474 [INFO] [stderr] 5: 0x5635c1063e01 - std::panicking::continue_panic_fmt::ha6d6ae144369025b [INFO] [stderr] at src/libstd/panicking.rs:381 [INFO] [stderr] 6: 0x5635c1063d4e - std::panicking::begin_panic_fmt::he54eae869ed71eb1 [INFO] [stderr] at src/libstd/panicking.rs:336 [INFO] [stderr] 7: 0x5635c1055de0 - build_script_build::panic_if_process_not_successul::h025fa5a17e7f4f2f [INFO] [stderr] at src/build.rs:44 [INFO] [stderr] 8: 0x5635c10558a4 - build_script_build::tool::h86ca975d803ff1af [INFO] [stderr] at src/build.rs:22 [INFO] [stderr] 9: 0x5635c105553a - build_script_build::main::h4a26be930c35d82d [INFO] [stderr] at src/build.rs:16 [INFO] [stderr] 10: 0x5635c104f78f - std::rt::lang_start::{{closure}}::hef080ae048e9af01 [INFO] [stderr] at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libstd/rt.rs:64 [INFO] [stderr] 11: 0x5635c1063cd2 - std::panicking::try::do_call::hc3d8373a0b215f51 [INFO] [stderr] at src/libstd/rt.rs:49 [INFO] [stderr] at src/libstd/panicking.rs:293 [INFO] [stderr] 12: 0x5635c106a059 - __rust_maybe_catch_panic [INFO] [stderr] at src/libpanic_unwind/lib.rs:85 [INFO] [stderr] 13: 0x5635c106478c - std::rt::lang_start_internal::he5218c8b95d395f2 [INFO] [stderr] at src/libstd/panicking.rs:272 [INFO] [stderr] at src/libstd/panic.rs:394 [INFO] [stderr] at src/libstd/rt.rs:48 [INFO] [stderr] 14: 0x5635c104f768 - std::rt::lang_start::h9ffa94ab8d27767b [INFO] [stderr] at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libstd/rt.rs:64 [INFO] [stderr] 15: 0x5635c1056119 - main [INFO] [stderr] 16: 0x7fde8422c2e0 - __libc_start_main [INFO] [stderr] 17: 0x5635c104a529 - _start [INFO] [stderr] 18: 0x0 - [INFO] [stderr] [INFO] running `"docker" "inspect" "80d4ef1c8e192e7d3ff576be358c403f5b7030f2f713d3388e1719119d0c250b"` [INFO] running `"docker" "rm" "-f" "80d4ef1c8e192e7d3ff576be358c403f5b7030f2f713d3388e1719119d0c250b"` [INFO] [stdout] 80d4ef1c8e192e7d3ff576be358c403f5b7030f2f713d3388e1719119d0c250b