Sep 02 16:05:07.270 INFO checking dpdk-ethernet-0.1.10 against master#1114ab684fbad001c4e580326d8eb4d8c4e917d3 for pr-53851 Sep 02 16:05:07.270 INFO running: cargo +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets Sep 02 16:05:07.271 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-3/pr-53851/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53851/worker-3/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 16:05:07.433 INFO blam! f9f27370eabf0fce80ddc79fc18eae6b3769e8c7c93e1810fdc69a5e2add4c25 Sep 02 16:05:07.435 INFO running `"docker" "start" "-a" "f9f27370eabf0fce80ddc79fc18eae6b3769e8c7c93e1810fdc69a5e2add4c25"` Sep 02 16:05:08.167 INFO kablam! Compiling libnuma-sys v0.0.9 Sep 02 16:05:08.167 INFO kablam! Compiling rdma-core-sys v0.1.10 Sep 02 16:05:08.167 INFO kablam! Checking hyper-thread-random v0.4.2 Sep 02 16:05:08.171 INFO kablam! Checking dpdk-unix v0.1.1 Sep 02 16:05:08.171 INFO kablam! Checking network-endian v0.1.5 Sep 02 16:05:08.171 INFO kablam! Checking network-time v0.1.1 Sep 02 16:05:08.343 INFO kablam! error: failed to run custom build command for `libnuma-sys v0.0.9` Sep 02 16:05:08.343 INFO kablam! process didn't exit successfully: `/target/debug/build/libnuma-sys-d56664a04c66fa55/build-script-build` (exit code: 101) Sep 02 16:05:08.343 INFO kablam! --- stderr Sep 02 16:05:08.343 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 Sep 02 16:05:08.343 INFO kablam! compile-rdma-core:The binary 'x86_64-linux-musl-ar' needs to be in the path Sep 02 16:05:08.343 INFO kablam! compile-rdma-core:FAIL:Please make sure that the missing binaries are installed because 'make' Sep 02 16:05:08.343 INFO kablam! ')', /cargo-home/registry/src/github.com-1ecc6299db9ec823/libnuma-sys-0.0.9/src/build.rs:44:2 Sep 02 16:05:08.343 INFO kablam! stack backtrace: Sep 02 16:05:08.343 INFO kablam! 0: 0x5558da2987ee - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::ha200f2cd684ebd49 Sep 02 16:05:08.343 INFO kablam! at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49 Sep 02 16:05:08.343 INFO kablam! 1: 0x5558da28ab36 - std::sys_common::backtrace::print::hfe3d4e47b4c8e48c Sep 02 16:05:08.343 INFO kablam! at libstd/sys_common/backtrace.rs:71 Sep 02 16:05:08.343 INFO kablam! at libstd/sys_common/backtrace.rs:59 Sep 02 16:05:08.343 INFO kablam! 2: 0x5558da28943d - std::panicking::default_hook::{{closure}}::hf56af31102a42941 Sep 02 16:05:08.343 INFO kablam! at libstd/panicking.rs:211 Sep 02 16:05:08.344 INFO kablam! 3: 0x5558da2891b0 - std::panicking::default_hook::ha51b5d4eb7ec526d Sep 02 16:05:08.344 INFO kablam! at libstd/panicking.rs:227 Sep 02 16:05:08.344 INFO kablam! 4: 0x5558da2899fc - std::panicking::rust_panic_with_hook::hd585483f9daec810 Sep 02 16:05:08.344 INFO kablam! at libstd/panicking.rs:477 Sep 02 16:05:08.344 INFO kablam! 5: 0x5558da2895f9 - std::panicking::continue_panic_fmt::h918075cde557b461 Sep 02 16:05:08.344 INFO kablam! at libstd/panicking.rs:391 Sep 02 16:05:08.344 INFO kablam! 6: 0x5558da28955d - std::panicking::begin_panic_fmt::h5e5c6b72bacdc05a Sep 02 16:05:08.344 INFO kablam! at libstd/panicking.rs:346 Sep 02 16:05:08.344 INFO kablam! 7: 0x5558da285841 - build_script_build::panic_if_process_not_successul::h678320bfb41031ff Sep 02 16:05:08.344 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/libnuma-sys-0.0.9/src/build.rs:44 Sep 02 16:05:08.344 INFO kablam! 8: 0x5558da2852e7 - build_script_build::tool::h1c3260e499bd1948 Sep 02 16:05:08.344 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/libnuma-sys-0.0.9/src/build.rs:22 Sep 02 16:05:08.344 INFO kablam! 9: 0x5558da284f2e - build_script_build::main::hd7d7d36d69fe1c8c Sep 02 16:05:08.344 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/libnuma-sys-0.0.9/src/build.rs:16 Sep 02 16:05:08.344 INFO kablam! 10: 0x5558da28265f - std::rt::lang_start::{{closure}}::h64b2e38cb461f8fc Sep 02 16:05:08.344 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 16:05:08.344 INFO kablam! 11: 0x5558da2894e2 - std::panicking::try::do_call::hea63f5620482e896 Sep 02 16:05:08.344 INFO kablam! at libstd/rt.rs:59 Sep 02 16:05:08.344 INFO kablam! at libstd/panicking.rs:310 Sep 02 16:05:08.344 INFO kablam! 12: 0x5558da2aa6d9 - __rust_maybe_catch_panic Sep 02 16:05:08.344 INFO kablam! at libpanic_unwind/lib.rs:103 Sep 02 16:05:08.344 INFO kablam! 13: 0x5558da294405 - std::rt::lang_start_internal::hfd6e69240f0360f8 Sep 02 16:05:08.345 INFO kablam! at libstd/panicking.rs:289 Sep 02 16:05:08.345 INFO kablam! at libstd/panic.rs:392 Sep 02 16:05:08.345 INFO kablam! at libstd/rt.rs:58 Sep 02 16:05:08.345 INFO kablam! 14: 0x5558da282637 - std::rt::lang_start::hc1c0f2c657b37fd4 Sep 02 16:05:08.345 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 16:05:08.345 INFO kablam! 15: 0x5558da285b89 - main Sep 02 16:05:08.345 INFO kablam! 16: 0x7fdb36d7e82f - __libc_start_main Sep 02 16:05:08.345 INFO kablam! 17: 0x5558da27fdf8 - _start Sep 02 16:05:08.345 INFO kablam! 18: 0x0 - Sep 02 16:05:08.345 INFO kablam! Sep 02 16:05:08.345 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 02 16:05:08.359 INFO kablam! error: failed to run custom build command for `rdma-core-sys v0.1.10` Sep 02 16:05:08.359 INFO kablam! process didn't exit successfully: `/target/debug/build/rdma-core-sys-d56aec9d2cfd8b78/build-script-build` (exit code: 101) Sep 02 16:05:08.359 INFO kablam! --- stderr Sep 02 16:05:08.359 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 Sep 02 16:05:08.359 INFO kablam! compile-rdma-core:The binary 'x86_64-linux-musl-ar' needs to be in the path Sep 02 16:05:08.359 INFO kablam! compile-rdma-core:FAIL:Please make sure that the missing binaries are installed because 'make' Sep 02 16:05:08.359 INFO kablam! ')', /cargo-home/registry/src/github.com-1ecc6299db9ec823/rdma-core-sys-0.1.10/src/build.rs:80:2 Sep 02 16:05:08.359 INFO kablam! stack backtrace: Sep 02 16:05:08.359 INFO kablam! 0: 0x562a19d6a7fe - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::ha200f2cd684ebd49 Sep 02 16:05:08.359 INFO kablam! at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49 Sep 02 16:05:08.359 INFO kablam! 1: 0x562a19d5a6a6 - std::sys_common::backtrace::print::hfe3d4e47b4c8e48c Sep 02 16:05:08.359 INFO kablam! at libstd/sys_common/backtrace.rs:71 Sep 02 16:05:08.359 INFO kablam! at libstd/sys_common/backtrace.rs:59 Sep 02 16:05:08.359 INFO kablam! 2: 0x562a19d589ed - std::panicking::default_hook::{{closure}}::hf56af31102a42941 Sep 02 16:05:08.359 INFO kablam! at libstd/panicking.rs:211 Sep 02 16:05:08.359 INFO kablam! 3: 0x562a19d58760 - std::panicking::default_hook::ha51b5d4eb7ec526d Sep 02 16:05:08.360 INFO kablam! at libstd/panicking.rs:227 Sep 02 16:05:08.360 INFO kablam! 4: 0x562a19d5905c - std::panicking::rust_panic_with_hook::hd585483f9daec810 Sep 02 16:05:08.360 INFO kablam! at libstd/panicking.rs:477 Sep 02 16:05:08.360 INFO kablam! 5: 0x562a19d58c59 - std::panicking::continue_panic_fmt::h918075cde557b461 Sep 02 16:05:08.360 INFO kablam! at libstd/panicking.rs:391 Sep 02 16:05:08.360 INFO kablam! 6: 0x562a19d58bbd - std::panicking::begin_panic_fmt::h5e5c6b72bacdc05a Sep 02 16:05:08.360 INFO kablam! at libstd/panicking.rs:346 Sep 02 16:05:08.360 INFO kablam! 7: 0x562a19ce8ef1 - build_script_build::panic_if_process_not_successful::hd49efd4e89077eb7 Sep 02 16:05:08.360 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/rdma-core-sys-0.1.10/src/build.rs:80 Sep 02 16:05:08.360 INFO kablam! 8: 0x562a19ce8997 - build_script_build::tool::h34b4453ff8a27cf7 Sep 02 16:05:08.360 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/rdma-core-sys-0.1.10/src/build.rs:58 Sep 02 16:05:08.360 INFO kablam! 9: 0x562a19ce7cb4 - build_script_build::main::h0ab32893dee8a0f0 Sep 02 16:05:08.360 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/rdma-core-sys-0.1.10/src/build.rs:23 Sep 02 16:05:08.360 INFO kablam! 10: 0x562a19ceacaf - std::rt::lang_start::{{closure}}::h8e0d4d5eccb8f811 Sep 02 16:05:08.360 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 16:05:08.360 INFO kablam! 11: 0x562a19d58af2 - std::panicking::try::do_call::hea63f5620482e896 Sep 02 16:05:08.360 INFO kablam! at libstd/rt.rs:59 Sep 02 16:05:08.360 INFO kablam! at libstd/panicking.rs:310 Sep 02 16:05:08.360 INFO kablam! 12: 0x562a19d7c3e9 - __rust_maybe_catch_panic Sep 02 16:05:08.360 INFO kablam! at libpanic_unwind/lib.rs:103 Sep 02 16:05:08.360 INFO kablam! 13: 0x562a19d65f75 - std::rt::lang_start_internal::hfd6e69240f0360f8 Sep 02 16:05:08.360 INFO kablam! at libstd/panicking.rs:289 Sep 02 16:05:08.360 INFO kablam! at libstd/panic.rs:392 Sep 02 16:05:08.360 INFO kablam! at libstd/rt.rs:58 Sep 02 16:05:08.360 INFO kablam! 14: 0x562a19ceac87 - std::rt::lang_start::ha74fda8d062f6051 Sep 02 16:05:08.360 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 16:05:08.360 INFO kablam! 15: 0x562a19ce91e9 - main Sep 02 16:05:08.360 INFO kablam! 16: 0x7fbeca9ba82f - __libc_start_main Sep 02 16:05:08.360 INFO kablam! 17: 0x562a19ce7b18 - _start Sep 02 16:05:08.360 INFO kablam! 18: 0x0 - Sep 02 16:05:08.361 INFO kablam! Sep 02 16:05:08.361 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 02 16:05:09.551 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u16` in the current scope Sep 02 16:05:09.552 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:16:16 Sep 02 16:05:09.552 INFO kablam! | Sep 02 16:05:09.552 INFO kablam! 16 | u16::from_be(u16::from_bytes(self.0)).partial_cmp(&u16::from_be(u16::from_bytes(other.0))) Sep 02 16:05:09.552 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u16` Sep 02 16:05:09.552 INFO kablam! | Sep 02 16:05:09.552 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.552 INFO kablam! Sep 02 16:05:09.562 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u16` in the current scope Sep 02 16:05:09.562 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:16:67 Sep 02 16:05:09.562 INFO kablam! | Sep 02 16:05:09.562 INFO kablam! 16 | u16::from_be(u16::from_bytes(self.0)).partial_cmp(&u16::from_be(u16::from_bytes(other.0))) Sep 02 16:05:09.562 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u16` Sep 02 16:05:09.562 INFO kablam! | Sep 02 16:05:09.562 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.562 INFO kablam! Sep 02 16:05:09.565 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u16` in the current scope Sep 02 16:05:09.565 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:25:16 Sep 02 16:05:09.565 INFO kablam! | Sep 02 16:05:09.565 INFO kablam! 25 | u16::from_be(u16::from_bytes(self.0)).cmp(&u16::from_be(u16::from_bytes(other.0))) Sep 02 16:05:09.565 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u16` Sep 02 16:05:09.565 INFO kablam! | Sep 02 16:05:09.565 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.565 INFO kablam! Sep 02 16:05:09.571 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u16` in the current scope Sep 02 16:05:09.571 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:25:59 Sep 02 16:05:09.571 INFO kablam! | Sep 02 16:05:09.571 INFO kablam! 25 | u16::from_be(u16::from_bytes(self.0)).cmp(&u16::from_be(u16::from_bytes(other.0))) Sep 02 16:05:09.571 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u16` Sep 02 16:05:09.571 INFO kablam! | Sep 02 16:05:09.572 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.572 INFO kablam! Sep 02 16:05:09.589 INFO kablam! error[E0599]: no method named `to_bytes` found for type `u16` in the current scope Sep 02 16:05:09.589 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:113:42 Sep 02 16:05:09.589 INFO kablam! | Sep 02 16:05:09.589 INFO kablam! 113 | NetworkEndianU16(native_endian.to_be().to_bytes()) Sep 02 16:05:09.589 INFO kablam! | ^^^^^^^^ Sep 02 16:05:09.589 INFO kablam! | Sep 02 16:05:09.589 INFO kablam! = help: items from traits can only be used if the trait is implemented and in scope Sep 02 16:05:09.589 INFO kablam! = note: the following trait defines an item `to_bytes`, perhaps you need to implement it: Sep 02 16:05:09.589 INFO kablam! candidate #1: `NetworkEndian` Sep 02 16:05:09.589 INFO kablam! Sep 02 16:05:09.592 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u16` in the current scope Sep 02 16:05:09.592 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:126:3 Sep 02 16:05:09.592 INFO kablam! | Sep 02 16:05:09.592 INFO kablam! 126 | u16::from_bytes(self.0) Sep 02 16:05:09.592 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u16` Sep 02 16:05:09.592 INFO kablam! | Sep 02 16:05:09.592 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.592 INFO kablam! Sep 02 16:05:09.642 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u32` in the current scope Sep 02 16:05:09.643 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:16:16 Sep 02 16:05:09.643 INFO kablam! | Sep 02 16:05:09.643 INFO kablam! 16 | u32::from_be(u32::from_bytes(self.0)).partial_cmp(&u32::from_be(u32::from_bytes(other.0))) Sep 02 16:05:09.643 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u32` Sep 02 16:05:09.643 INFO kablam! | Sep 02 16:05:09.643 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.643 INFO kablam! Sep 02 16:05:09.645 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u32` in the current scope Sep 02 16:05:09.645 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:16:67 Sep 02 16:05:09.645 INFO kablam! | Sep 02 16:05:09.645 INFO kablam! 16 | u32::from_be(u32::from_bytes(self.0)).partial_cmp(&u32::from_be(u32::from_bytes(other.0))) Sep 02 16:05:09.645 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u32` Sep 02 16:05:09.645 INFO kablam! | Sep 02 16:05:09.645 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.645 INFO kablam! Sep 02 16:05:09.652 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u32` in the current scope Sep 02 16:05:09.652 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:25:16 Sep 02 16:05:09.652 INFO kablam! | Sep 02 16:05:09.652 INFO kablam! 25 | u32::from_be(u32::from_bytes(self.0)).cmp(&u32::from_be(u32::from_bytes(other.0))) Sep 02 16:05:09.652 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u32` Sep 02 16:05:09.652 INFO kablam! | Sep 02 16:05:09.652 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.652 INFO kablam! Sep 02 16:05:09.654 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u32` in the current scope Sep 02 16:05:09.654 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:25:59 Sep 02 16:05:09.654 INFO kablam! | Sep 02 16:05:09.654 INFO kablam! 25 | u32::from_be(u32::from_bytes(self.0)).cmp(&u32::from_be(u32::from_bytes(other.0))) Sep 02 16:05:09.654 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u32` Sep 02 16:05:09.654 INFO kablam! | Sep 02 16:05:09.654 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.654 INFO kablam! Sep 02 16:05:09.666 INFO kablam! error[E0599]: no method named `to_bytes` found for type `u32` in the current scope Sep 02 16:05:09.666 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:116:42 Sep 02 16:05:09.666 INFO kablam! | Sep 02 16:05:09.666 INFO kablam! 116 | NetworkEndianU32(native_endian.to_be().to_bytes()) Sep 02 16:05:09.666 INFO kablam! | ^^^^^^^^ Sep 02 16:05:09.666 INFO kablam! | Sep 02 16:05:09.667 INFO kablam! = help: items from traits can only be used if the trait is implemented and in scope Sep 02 16:05:09.667 INFO kablam! = note: the following trait defines an item `to_bytes`, perhaps you need to implement it: Sep 02 16:05:09.667 INFO kablam! candidate #1: `NetworkEndian` Sep 02 16:05:09.667 INFO kablam! Sep 02 16:05:09.668 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u32` in the current scope Sep 02 16:05:09.668 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:129:3 Sep 02 16:05:09.668 INFO kablam! | Sep 02 16:05:09.668 INFO kablam! 129 | u32::from_bytes(self.0) Sep 02 16:05:09.669 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u32` Sep 02 16:05:09.670 INFO kablam! | Sep 02 16:05:09.671 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.671 INFO kablam! Sep 02 16:05:09.717 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u128` in the current scope Sep 02 16:05:09.717 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:16:17 Sep 02 16:05:09.717 INFO kablam! | Sep 02 16:05:09.717 INFO kablam! 16 | u128::from_be(u128::from_bytes(self.0)).partial_cmp(&u128::from_be(u128::from_bytes(other.0))) Sep 02 16:05:09.718 INFO kablam! | ^^^^^^^^^^^^^^^^ function or associated item not found in `u128` Sep 02 16:05:09.723 INFO kablam! | Sep 02 16:05:09.723 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.723 INFO kablam! Sep 02 16:05:09.725 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u128` in the current scope Sep 02 16:05:09.725 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:16:70 Sep 02 16:05:09.725 INFO kablam! | Sep 02 16:05:09.725 INFO kablam! 16 | u128::from_be(u128::from_bytes(self.0)).partial_cmp(&u128::from_be(u128::from_bytes(other.0))) Sep 02 16:05:09.725 INFO kablam! | ^^^^^^^^^^^^^^^^ function or associated item not found in `u128` Sep 02 16:05:09.726 INFO kablam! | Sep 02 16:05:09.726 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.726 INFO kablam! Sep 02 16:05:09.728 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u128` in the current scope Sep 02 16:05:09.728 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:25:17 Sep 02 16:05:09.728 INFO kablam! | Sep 02 16:05:09.728 INFO kablam! 25 | u128::from_be(u128::from_bytes(self.0)).cmp(&u128::from_be(u128::from_bytes(other.0))) Sep 02 16:05:09.729 INFO kablam! | ^^^^^^^^^^^^^^^^ function or associated item not found in `u128` Sep 02 16:05:09.729 INFO kablam! | Sep 02 16:05:09.729 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.729 INFO kablam! Sep 02 16:05:09.731 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u128` in the current scope Sep 02 16:05:09.731 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:25:62 Sep 02 16:05:09.731 INFO kablam! | Sep 02 16:05:09.731 INFO kablam! 25 | u128::from_be(u128::from_bytes(self.0)).cmp(&u128::from_be(u128::from_bytes(other.0))) Sep 02 16:05:09.731 INFO kablam! | ^^^^^^^^^^^^^^^^ function or associated item not found in `u128` Sep 02 16:05:09.731 INFO kablam! | Sep 02 16:05:09.731 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.731 INFO kablam! Sep 02 16:05:09.755 INFO kablam! error[E0599]: no method named `to_bytes` found for type `u128` in the current scope Sep 02 16:05:09.755 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:113:43 Sep 02 16:05:09.755 INFO kablam! | Sep 02 16:05:09.755 INFO kablam! 113 | NetworkEndianU128(native_endian.to_be().to_bytes()) Sep 02 16:05:09.755 INFO kablam! | ^^^^^^^^ Sep 02 16:05:09.755 INFO kablam! | Sep 02 16:05:09.755 INFO kablam! = help: items from traits can only be used if the trait is implemented and in scope Sep 02 16:05:09.755 INFO kablam! = note: the following trait defines an item `to_bytes`, perhaps you need to implement it: Sep 02 16:05:09.755 INFO kablam! candidate #1: `NetworkEndian` Sep 02 16:05:09.755 INFO kablam! Sep 02 16:05:09.757 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u128` in the current scope Sep 02 16:05:09.757 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:126:3 Sep 02 16:05:09.757 INFO kablam! | Sep 02 16:05:09.757 INFO kablam! 126 | u128::from_bytes(self.0) Sep 02 16:05:09.758 INFO kablam! | ^^^^^^^^^^^^^^^^ function or associated item not found in `u128` Sep 02 16:05:09.758 INFO kablam! | Sep 02 16:05:09.758 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.758 INFO kablam! Sep 02 16:05:09.768 INFO kablam! error: aborting due to 18 previous errors Sep 02 16:05:09.768 INFO kablam! Sep 02 16:05:09.768 INFO kablam! For more information about this error, try `rustc --explain E0599`. Sep 02 16:05:09.790 INFO kablam! error: Could not compile `network-endian`. Sep 02 16:05:09.790 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 02 16:05:12.185 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u64` in the current scope Sep 02 16:05:12.185 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/dpdk-unix-0.1.1/src/android_linux/page_table/PageMapEntry.rs:111:19 Sep 02 16:05:12.185 INFO kablam! | Sep 02 16:05:12.185 INFO kablam! 111 | Ok(PageMapEntry(u64::from_bytes(buffer))) Sep 02 16:05:12.185 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u64` Sep 02 16:05:12.185 INFO kablam! | Sep 02 16:05:12.185 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:12.185 INFO kablam! Sep 02 16:05:12.243 INFO kablam! error[E0308]: mismatched types Sep 02 16:05:12.243 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/dpdk-unix-0.1.1/src/android_linux/pci/PciBusInformation.rs:88:76 Sep 02 16:05:12.243 INFO kablam! | Sep 02 16:05:12.243 INFO kablam! 88 | let raw_pci_bus_address = match unsafe { ioctl(socket_file_descriptor.0, SIOCETHTOOL, &mut interface_request as *mut _ as *mut c_void) } Sep 02 16:05:12.243 INFO kablam! | ^^^^^^^^^^^ expected u64, found i32 Sep 02 16:05:12.243 INFO kablam! Sep 02 16:05:13.527 INFO kablam! error: aborting due to 2 previous errors Sep 02 16:05:13.527 INFO kablam! Sep 02 16:05:13.527 INFO kablam! Some errors occurred: E0308, E0599. Sep 02 16:05:13.527 INFO kablam! For more information about an error, try `rustc --explain E0308`. Sep 02 16:05:13.553 INFO kablam! error: Could not compile `dpdk-unix`. Sep 02 16:05:13.553 INFO kablam! Sep 02 16:05:13.553 INFO kablam! To learn more, run the command again with --verbose. Sep 02 16:05:13.554 INFO kablam! su: No module specific data is present Sep 02 16:05:14.078 INFO running `"docker" "rm" "-f" "f9f27370eabf0fce80ddc79fc18eae6b3769e8c7c93e1810fdc69a5e2add4c25"` Sep 02 16:05:14.226 INFO blam! f9f27370eabf0fce80ddc79fc18eae6b3769e8c7c93e1810fdc69a5e2add4c25