Sep 02 16:05:06.667 INFO checking dpdk-ethernet-0.1.10 against try#952c7dbfa2628309f557b367929ffc17af20b332 for pr-53851 Sep 02 16:05:06.667 INFO running: cargo +952c7dbfa2628309f557b367929ffc17af20b332-alt check --frozen --all --all-targets Sep 02 16:05:06.667 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 16:05:06.833 INFO blam! ae909b5e539a4df058543eebc6e6a3e18df08abe479a543d6d0e12f4e80b30a9 Sep 02 16:05:06.835 INFO running `"docker" "start" "-a" "ae909b5e539a4df058543eebc6e6a3e18df08abe479a543d6d0e12f4e80b30a9"` Sep 02 16:05:07.776 INFO kablam! Compiling libnuma-sys v0.0.9 Sep 02 16:05:07.776 INFO kablam! Compiling rdma-core-sys v0.1.10 Sep 02 16:05:07.776 INFO kablam! Checking hyper-thread-random v0.4.2 Sep 02 16:05:07.779 INFO kablam! Checking dpdk-unix v0.1.1 Sep 02 16:05:07.779 INFO kablam! Checking network-time v0.1.1 Sep 02 16:05:07.779 INFO kablam! Checking network-endian v0.1.5 Sep 02 16:05:07.817 INFO kablam! error: failed to run custom build command for `rdma-core-sys v0.1.10` Sep 02 16:05:07.817 INFO kablam! process didn't exit successfully: `/target/debug/build/rdma-core-sys-59e37517db2ae578/build-script-build` (exit code: 101) Sep 02 16:05:07.817 INFO kablam! --- stderr Sep 02 16:05:07.817 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:07.817 INFO kablam! compile-rdma-core:The binary 'x86_64-linux-musl-ar' needs to be in the path Sep 02 16:05:07.818 INFO kablam! compile-rdma-core:FAIL:Please make sure that the missing binaries are installed because 'make' Sep 02 16:05:07.818 INFO kablam! ')', /cargo-home/registry/src/github.com-1ecc6299db9ec823/rdma-core-sys-0.1.10/src/build.rs:80:2 Sep 02 16:05:07.818 INFO kablam! stack backtrace: Sep 02 16:05:07.818 INFO kablam! 0: 0x55a6674477fe - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h8608d381b52a1cc7 Sep 02 16:05:07.818 INFO kablam! at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49 Sep 02 16:05:07.818 INFO kablam! 1: 0x55a6674376a6 - std::sys_common::backtrace::print::hf96fbb6301ca8111 Sep 02 16:05:07.818 INFO kablam! at libstd/sys_common/backtrace.rs:71 Sep 02 16:05:07.818 INFO kablam! at libstd/sys_common/backtrace.rs:59 Sep 02 16:05:07.818 INFO kablam! 2: 0x55a6674359ed - std::panicking::default_hook::{{closure}}::h2e8fa0d6ce9ebecc Sep 02 16:05:07.818 INFO kablam! at libstd/panicking.rs:211 Sep 02 16:05:07.818 INFO kablam! 3: 0x55a667435760 - std::panicking::default_hook::h3e385661c8d6b6f8 Sep 02 16:05:07.818 INFO kablam! at libstd/panicking.rs:227 Sep 02 16:05:07.818 INFO kablam! 4: 0x55a66743605c - std::panicking::rust_panic_with_hook::h82448672ce6401e7 Sep 02 16:05:07.818 INFO kablam! at libstd/panicking.rs:477 Sep 02 16:05:07.818 INFO kablam! 5: 0x55a667435c59 - std::panicking::continue_panic_fmt::h7abacf9371d614d8 Sep 02 16:05:07.818 INFO kablam! at libstd/panicking.rs:391 Sep 02 16:05:07.818 INFO kablam! 6: 0x55a667435bbd - std::panicking::begin_panic_fmt::h7b5ce7842a1f14ab Sep 02 16:05:07.818 INFO kablam! at libstd/panicking.rs:346 Sep 02 16:05:07.818 INFO kablam! 7: 0x55a6673c5ef1 - build_script_build::panic_if_process_not_successful::hcf1e5abf7f2459d5 Sep 02 16:05:07.818 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/rdma-core-sys-0.1.10/src/build.rs:80 Sep 02 16:05:07.818 INFO kablam! 8: 0x55a6673c5997 - build_script_build::tool::h2b0f79746dd968cf Sep 02 16:05:07.818 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/rdma-core-sys-0.1.10/src/build.rs:58 Sep 02 16:05:07.818 INFO kablam! 9: 0x55a6673c4cb4 - build_script_build::main::hf8203dbe7fb46bfe Sep 02 16:05:07.818 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/rdma-core-sys-0.1.10/src/build.rs:23 Sep 02 16:05:07.818 INFO kablam! 10: 0x55a6673c7caf - std::rt::lang_start::{{closure}}::h1759c9346f1ab3ac Sep 02 16:05:07.818 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 16:05:07.818 INFO kablam! 11: 0x55a667435af2 - std::panicking::try::do_call::he8eb7284c711bc58 Sep 02 16:05:07.818 INFO kablam! at libstd/rt.rs:59 Sep 02 16:05:07.818 INFO kablam! at libstd/panicking.rs:310 Sep 02 16:05:07.818 INFO kablam! 12: 0x55a6674593f9 - __rust_maybe_catch_panic Sep 02 16:05:07.818 INFO kablam! at libpanic_unwind/lib.rs:103 Sep 02 16:05:07.818 INFO kablam! 13: 0x55a667442f75 - std::rt::lang_start_internal::h25421c11e0cff495 Sep 02 16:05:07.818 INFO kablam! at libstd/panicking.rs:289 Sep 02 16:05:07.818 INFO kablam! at libstd/panic.rs:392 Sep 02 16:05:07.818 INFO kablam! at libstd/rt.rs:58 Sep 02 16:05:07.819 INFO kablam! 14: 0x55a6673c7c87 - std::rt::lang_start::h969ceda71e85feea Sep 02 16:05:07.819 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 16:05:07.819 INFO kablam! 15: 0x55a6673c61e9 - main Sep 02 16:05:07.819 INFO kablam! 16: 0x7f3a6baf482f - __libc_start_main Sep 02 16:05:07.819 INFO kablam! 17: 0x55a6673c4b18 - _start Sep 02 16:05:07.819 INFO kablam! 18: 0x0 - Sep 02 16:05:07.819 INFO kablam! Sep 02 16:05:07.819 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 02 16:05:07.824 INFO kablam! error: failed to run custom build command for `libnuma-sys v0.0.9` Sep 02 16:05:07.824 INFO kablam! process didn't exit successfully: `/target/debug/build/libnuma-sys-30cf375e68a2a90a/build-script-build` (exit code: 101) Sep 02 16:05:07.824 INFO kablam! --- stderr Sep 02 16:05:07.824 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:07.824 INFO kablam! compile-rdma-core:The binary 'x86_64-linux-musl-ar' needs to be in the path Sep 02 16:05:07.824 INFO kablam! compile-rdma-core:FAIL:Please make sure that the missing binaries are installed because 'make' Sep 02 16:05:07.824 INFO kablam! ')', /cargo-home/registry/src/github.com-1ecc6299db9ec823/libnuma-sys-0.0.9/src/build.rs:44:2 Sep 02 16:05:07.824 INFO kablam! stack backtrace: Sep 02 16:05:07.824 INFO kablam! 0: 0x55aede7817ee - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h8608d381b52a1cc7 Sep 02 16:05:07.824 INFO kablam! at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49 Sep 02 16:05:07.824 INFO kablam! 1: 0x55aede773b36 - std::sys_common::backtrace::print::hf96fbb6301ca8111 Sep 02 16:05:07.824 INFO kablam! at libstd/sys_common/backtrace.rs:71 Sep 02 16:05:07.824 INFO kablam! at libstd/sys_common/backtrace.rs:59 Sep 02 16:05:07.824 INFO kablam! 2: 0x55aede77243d - std::panicking::default_hook::{{closure}}::h2e8fa0d6ce9ebecc Sep 02 16:05:07.824 INFO kablam! at libstd/panicking.rs:211 Sep 02 16:05:07.824 INFO kablam! 3: 0x55aede7721b0 - std::panicking::default_hook::h3e385661c8d6b6f8 Sep 02 16:05:07.824 INFO kablam! at libstd/panicking.rs:227 Sep 02 16:05:07.824 INFO kablam! 4: 0x55aede7729fc - std::panicking::rust_panic_with_hook::h82448672ce6401e7 Sep 02 16:05:07.824 INFO kablam! at libstd/panicking.rs:477 Sep 02 16:05:07.825 INFO kablam! 5: 0x55aede7725f9 - std::panicking::continue_panic_fmt::h7abacf9371d614d8 Sep 02 16:05:07.825 INFO kablam! at libstd/panicking.rs:391 Sep 02 16:05:07.825 INFO kablam! 6: 0x55aede77255d - std::panicking::begin_panic_fmt::h7b5ce7842a1f14ab Sep 02 16:05:07.825 INFO kablam! at libstd/panicking.rs:346 Sep 02 16:05:07.825 INFO kablam! 7: 0x55aede76e841 - build_script_build::panic_if_process_not_successul::h1eaf69f9ceb4ec0f Sep 02 16:05:07.825 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/libnuma-sys-0.0.9/src/build.rs:44 Sep 02 16:05:07.825 INFO kablam! 8: 0x55aede76e2e7 - build_script_build::tool::h639e7b0274eab084 Sep 02 16:05:07.825 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/libnuma-sys-0.0.9/src/build.rs:22 Sep 02 16:05:07.825 INFO kablam! 9: 0x55aede76df2e - build_script_build::main::h75927c0fa0fb0e18 Sep 02 16:05:07.825 INFO kablam! at /cargo-home/registry/src/github.com-1ecc6299db9ec823/libnuma-sys-0.0.9/src/build.rs:16 Sep 02 16:05:07.825 INFO kablam! 10: 0x55aede76b65f - std::rt::lang_start::{{closure}}::h536d78e42ef3d269 Sep 02 16:05:07.825 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 16:05:07.825 INFO kablam! 11: 0x55aede7724e2 - std::panicking::try::do_call::he8eb7284c711bc58 Sep 02 16:05:07.825 INFO kablam! at libstd/rt.rs:59 Sep 02 16:05:07.825 INFO kablam! at libstd/panicking.rs:310 Sep 02 16:05:07.825 INFO kablam! 12: 0x55aede7936e9 - __rust_maybe_catch_panic Sep 02 16:05:07.825 INFO kablam! at libpanic_unwind/lib.rs:103 Sep 02 16:05:07.825 INFO kablam! 13: 0x55aede77d405 - std::rt::lang_start_internal::h25421c11e0cff495 Sep 02 16:05:07.825 INFO kablam! at libstd/panicking.rs:289 Sep 02 16:05:07.825 INFO kablam! at libstd/panic.rs:392 Sep 02 16:05:07.826 INFO kablam! at libstd/rt.rs:58 Sep 02 16:05:07.826 INFO kablam! 14: 0x55aede76b637 - std::rt::lang_start::h2c3184d584988a60 Sep 02 16:05:07.826 INFO kablam! at /checkout/src/libstd/rt.rs:74 Sep 02 16:05:07.826 INFO kablam! 15: 0x55aede76eb89 - main Sep 02 16:05:07.826 INFO kablam! 16: 0x7facb1be082f - __libc_start_main Sep 02 16:05:07.826 INFO kablam! 17: 0x55aede768df8 - _start Sep 02 16:05:07.826 INFO kablam! 18: 0x0 - Sep 02 16:05:07.826 INFO kablam! Sep 02 16:05:07.826 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 02 16:05:08.997 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u16` in the current scope Sep 02 16:05:08.997 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:16:16 Sep 02 16:05:08.997 INFO kablam! | Sep 02 16:05:08.997 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:08.997 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u16` Sep 02 16:05:08.997 INFO kablam! | Sep 02 16:05:08.997 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:08.997 INFO kablam! Sep 02 16:05:09.011 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.011 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:16:67 Sep 02 16:05:09.011 INFO kablam! | Sep 02 16:05:09.011 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.011 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u16` Sep 02 16:05:09.011 INFO kablam! | Sep 02 16:05:09.011 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.011 INFO kablam! Sep 02 16:05:09.016 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.016 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:25:16 Sep 02 16:05:09.016 INFO kablam! | Sep 02 16:05:09.016 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.016 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u16` Sep 02 16:05:09.016 INFO kablam! | Sep 02 16:05:09.016 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.016 INFO kablam! Sep 02 16:05:09.016 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.016 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:25:59 Sep 02 16:05:09.016 INFO kablam! | Sep 02 16:05:09.016 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.017 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u16` Sep 02 16:05:09.017 INFO kablam! | Sep 02 16:05:09.017 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.017 INFO kablam! Sep 02 16:05:09.045 INFO kablam! error[E0599]: no method named `to_bytes` found for type `u16` in the current scope Sep 02 16:05:09.045 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:113:42 Sep 02 16:05:09.045 INFO kablam! | Sep 02 16:05:09.045 INFO kablam! 113 | NetworkEndianU16(native_endian.to_be().to_bytes()) Sep 02 16:05:09.045 INFO kablam! | ^^^^^^^^ Sep 02 16:05:09.045 INFO kablam! | Sep 02 16:05:09.045 INFO kablam! = help: items from traits can only be used if the trait is implemented and in scope Sep 02 16:05:09.045 INFO kablam! = note: the following trait defines an item `to_bytes`, perhaps you need to implement it: Sep 02 16:05:09.045 INFO kablam! candidate #1: `NetworkEndian` Sep 02 16:05:09.045 INFO kablam! Sep 02 16:05:09.051 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.051 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU16.rs:126:3 Sep 02 16:05:09.051 INFO kablam! | Sep 02 16:05:09.051 INFO kablam! 126 | u16::from_bytes(self.0) Sep 02 16:05:09.051 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u16` Sep 02 16:05:09.051 INFO kablam! | Sep 02 16:05:09.051 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.051 INFO kablam! Sep 02 16:05:09.120 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.120 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:16:16 Sep 02 16:05:09.120 INFO kablam! | Sep 02 16:05:09.120 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.121 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u32` Sep 02 16:05:09.121 INFO kablam! | Sep 02 16:05:09.121 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.121 INFO kablam! Sep 02 16:05:09.123 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.123 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:16:67 Sep 02 16:05:09.123 INFO kablam! | Sep 02 16:05:09.123 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.123 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u32` Sep 02 16:05:09.123 INFO kablam! | Sep 02 16:05:09.123 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.123 INFO kablam! Sep 02 16:05:09.125 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.125 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:25:16 Sep 02 16:05:09.125 INFO kablam! | Sep 02 16:05:09.126 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.126 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u32` Sep 02 16:05:09.126 INFO kablam! | Sep 02 16:05:09.126 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.126 INFO kablam! Sep 02 16:05:09.140 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.140 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:25:59 Sep 02 16:05:09.140 INFO kablam! | Sep 02 16:05:09.140 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.140 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u32` Sep 02 16:05:09.140 INFO kablam! | Sep 02 16:05:09.140 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.140 INFO kablam! Sep 02 16:05:09.147 INFO kablam! error[E0599]: no method named `to_bytes` found for type `u32` in the current scope Sep 02 16:05:09.147 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:116:42 Sep 02 16:05:09.147 INFO kablam! | Sep 02 16:05:09.147 INFO kablam! 116 | NetworkEndianU32(native_endian.to_be().to_bytes()) Sep 02 16:05:09.147 INFO kablam! | ^^^^^^^^ Sep 02 16:05:09.147 INFO kablam! | Sep 02 16:05:09.147 INFO kablam! = help: items from traits can only be used if the trait is implemented and in scope Sep 02 16:05:09.147 INFO kablam! = note: the following trait defines an item `to_bytes`, perhaps you need to implement it: Sep 02 16:05:09.147 INFO kablam! candidate #1: `NetworkEndian` Sep 02 16:05:09.147 INFO kablam! Sep 02 16:05:09.149 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.149 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU32.rs:129:3 Sep 02 16:05:09.149 INFO kablam! | Sep 02 16:05:09.149 INFO kablam! 129 | u32::from_bytes(self.0) Sep 02 16:05:09.149 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u32` Sep 02 16:05:09.149 INFO kablam! | Sep 02 16:05:09.149 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.149 INFO kablam! Sep 02 16:05:09.234 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.234 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:16:17 Sep 02 16:05:09.234 INFO kablam! | Sep 02 16:05:09.234 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.234 INFO kablam! | ^^^^^^^^^^^^^^^^ function or associated item not found in `u128` Sep 02 16:05:09.234 INFO kablam! | Sep 02 16:05:09.234 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.234 INFO kablam! Sep 02 16:05:09.245 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.245 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:16:70 Sep 02 16:05:09.245 INFO kablam! | Sep 02 16:05:09.245 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.245 INFO kablam! | ^^^^^^^^^^^^^^^^ function or associated item not found in `u128` Sep 02 16:05:09.246 INFO kablam! | Sep 02 16:05:09.246 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.246 INFO kablam! Sep 02 16:05:09.255 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.255 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:25:17 Sep 02 16:05:09.255 INFO kablam! | Sep 02 16:05:09.255 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.255 INFO kablam! | ^^^^^^^^^^^^^^^^ function or associated item not found in `u128` Sep 02 16:05:09.255 INFO kablam! | Sep 02 16:05:09.255 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.255 INFO kablam! Sep 02 16:05:09.257 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.258 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:25:62 Sep 02 16:05:09.258 INFO kablam! | Sep 02 16:05:09.258 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.258 INFO kablam! | ^^^^^^^^^^^^^^^^ function or associated item not found in `u128` Sep 02 16:05:09.258 INFO kablam! | Sep 02 16:05:09.259 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.259 INFO kablam! Sep 02 16:05:09.283 INFO kablam! error[E0599]: no method named `to_bytes` found for type `u128` in the current scope Sep 02 16:05:09.283 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:113:43 Sep 02 16:05:09.283 INFO kablam! | Sep 02 16:05:09.283 INFO kablam! 113 | NetworkEndianU128(native_endian.to_be().to_bytes()) Sep 02 16:05:09.283 INFO kablam! | ^^^^^^^^ Sep 02 16:05:09.284 INFO kablam! | Sep 02 16:05:09.285 INFO kablam! = help: items from traits can only be used if the trait is implemented and in scope Sep 02 16:05:09.285 INFO kablam! = note: the following trait defines an item `to_bytes`, perhaps you need to implement it: Sep 02 16:05:09.285 INFO kablam! candidate #1: `NetworkEndian` Sep 02 16:05:09.286 INFO kablam! Sep 02 16:05:09.289 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.289 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/network-endian-0.1.5/src/NetworkEndianU128.rs:126:3 Sep 02 16:05:09.289 INFO kablam! | Sep 02 16:05:09.289 INFO kablam! 126 | u128::from_bytes(self.0) Sep 02 16:05:09.289 INFO kablam! | ^^^^^^^^^^^^^^^^ function or associated item not found in `u128` Sep 02 16:05:09.290 INFO kablam! | Sep 02 16:05:09.290 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:09.290 INFO kablam! Sep 02 16:05:09.310 INFO kablam! error: aborting due to 18 previous errors Sep 02 16:05:09.311 INFO kablam! Sep 02 16:05:09.312 INFO kablam! For more information about this error, try `rustc --explain E0599`. Sep 02 16:05:09.330 INFO kablam! error: Could not compile `network-endian`. Sep 02 16:05:09.331 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 02 16:05:11.759 INFO kablam! error[E0599]: no function or associated item named `from_bytes` found for type `u64` in the current scope Sep 02 16:05:11.759 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:11.759 INFO kablam! | Sep 02 16:05:11.759 INFO kablam! 111 | Ok(PageMapEntry(u64::from_bytes(buffer))) Sep 02 16:05:11.759 INFO kablam! | ^^^^^^^^^^^^^^^ function or associated item not found in `u64` Sep 02 16:05:11.759 INFO kablam! | Sep 02 16:05:11.759 INFO kablam! = help: did you mean `from_be`? Sep 02 16:05:11.760 INFO kablam! Sep 02 16:05:11.817 INFO kablam! error[E0308]: mismatched types Sep 02 16:05:11.817 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:11.817 INFO kablam! | Sep 02 16:05:11.817 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:11.817 INFO kablam! | ^^^^^^^^^^^ expected u64, found i32 Sep 02 16:05:11.817 INFO kablam! Sep 02 16:05:13.094 INFO kablam! error: aborting due to 2 previous errors Sep 02 16:05:13.094 INFO kablam! Sep 02 16:05:13.095 INFO kablam! Some errors occurred: E0308, E0599. Sep 02 16:05:13.095 INFO kablam! For more information about an error, try `rustc --explain E0308`. Sep 02 16:05:13.113 INFO kablam! error: Could not compile `dpdk-unix`. Sep 02 16:05:13.113 INFO kablam! Sep 02 16:05:13.113 INFO kablam! To learn more, run the command again with --verbose. Sep 02 16:05:13.116 INFO kablam! su: No module specific data is present Sep 02 16:05:13.618 INFO running `"docker" "rm" "-f" "ae909b5e539a4df058543eebc6e6a3e18df08abe479a543d6d0e12f4e80b30a9"` Sep 02 16:05:13.779 INFO blam! ae909b5e539a4df058543eebc6e6a3e18df08abe479a543d6d0e12f4e80b30a9