Aug 17 16:32:25.340 INFO checking nanomsg-0.5.0 against try#a5d98b025f62ace80fe9d2a15781f900fc42515e for pr-53426 Aug 17 16:32:25.340 INFO running: cargo +a5d98b025f62ace80fe9d2a15781f900fc42515e-alt check --frozen --all --all-targets Aug 17 16:32:25.340 INFO creating container for: cargo +a5d98b025f62ace80fe9d2a15781f900fc42515e-alt check --frozen --all --all-targets Aug 17 16:32:25.340 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-5/pr-53426/try#a5d98b025f62ace80fe9d2a15781f900fc42515e:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53426/worker-5/try#a5d98b025f62ace80fe9d2a15781f900fc42515e:/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 +a5d98b025f62ace80fe9d2a15781f900fc42515e-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "crater"` Aug 17 16:32:25.568 INFO blam! 016b1d64be1079e47ed69aab133983e9737582c0dbaf1ffe3c83e7464c81551d Aug 17 16:32:25.571 INFO running `"docker" "start" "-a" "016b1d64be1079e47ed69aab133983e9737582c0dbaf1ffe3c83e7464c81551d"` Aug 17 16:32:26.831 INFO kablam! Compiling nanomsg-sys v0.5.0 Aug 17 16:32:28.451 INFO kablam! Checking nanomsg v0.5.0 (file:///source) Aug 17 16:32:29.449 INFO kablam! error[E0425]: cannot find value `ENOTSUP` in module `nanomsg_sys` Aug 17 16:32:29.449 INFO kablam! --> src/result.rs:19:47 Aug 17 16:32:29.449 INFO kablam! | Aug 17 16:32:29.449 INFO kablam! 19 | OperationNotSupported = nanomsg_sys::ENOTSUP as isize, Aug 17 16:32:29.450 INFO kablam! | ^^^^^^^ not found in `nanomsg_sys` Aug 17 16:32:29.450 INFO kablam! help: possible candidates are found in other modules, you can import them into scope Aug 17 16:32:29.450 INFO kablam! | Aug 17 16:32:29.450 INFO kablam! 3 | use libc::ENOTSUP; Aug 17 16:32:29.450 INFO kablam! | Aug 17 16:32:29.450 INFO kablam! 3 | use nanomsg_sys::posix_consts::ENOTSUP; Aug 17 16:32:29.450 INFO kablam! | Aug 17 16:32:29.450 INFO kablam! Aug 17 16:32:29.450 INFO kablam! error[E0531]: cannot find unit struct/variant or constant `ENOTSUP` in module `nanomsg_sys` Aug 17 16:32:29.450 INFO kablam! --> src/result.rs:61:26 Aug 17 16:32:29.451 INFO kablam! | Aug 17 16:32:29.451 INFO kablam! 61 | nanomsg_sys::ENOTSUP => Error::OperationNotSupported , Aug 17 16:32:29.451 INFO kablam! | ^^^^^^^ not found in `nanomsg_sys` Aug 17 16:32:29.454 INFO kablam! help: possible candidates are found in other modules, you can import them into scope Aug 17 16:32:29.454 INFO kablam! | Aug 17 16:32:29.454 INFO kablam! 3 | use libc::ENOTSUP; Aug 17 16:32:29.454 INFO kablam! | Aug 17 16:32:29.454 INFO kablam! 3 | use nanomsg_sys::posix_consts::ENOTSUP; Aug 17 16:32:29.455 INFO kablam! | Aug 17 16:32:29.455 INFO kablam! Aug 17 16:32:29.514 INFO kablam! error[E0425]: cannot find value `ENOTSUP` in module `nanomsg_sys` Aug 17 16:32:29.514 INFO kablam! --> src/result.rs:19:47 Aug 17 16:32:29.514 INFO kablam! | Aug 17 16:32:29.514 INFO kablam! 19 | OperationNotSupported = nanomsg_sys::ENOTSUP as isize, Aug 17 16:32:29.514 INFO kablam! | ^^^^^^^ not found in `nanomsg_sys` Aug 17 16:32:29.514 INFO kablam! help: possible candidates are found in other modules, you can import them into scope Aug 17 16:32:29.514 INFO kablam! | Aug 17 16:32:29.514 INFO kablam! 3 | use libc::ENOTSUP; Aug 17 16:32:29.514 INFO kablam! | Aug 17 16:32:29.514 INFO kablam! 3 | use nanomsg_sys::posix_consts::ENOTSUP; Aug 17 16:32:29.514 INFO kablam! | Aug 17 16:32:29.514 INFO kablam! Aug 17 16:32:29.515 INFO kablam! error[E0531]: cannot find unit struct/variant or constant `ENOTSUP` in module `nanomsg_sys` Aug 17 16:32:29.516 INFO kablam! --> src/result.rs:61:26 Aug 17 16:32:29.516 INFO kablam! | Aug 17 16:32:29.516 INFO kablam! 61 | nanomsg_sys::ENOTSUP => Error::OperationNotSupported , Aug 17 16:32:29.516 INFO kablam! | ^^^^^^^ not found in `nanomsg_sys` Aug 17 16:32:29.516 INFO kablam! help: possible candidates are found in other modules, you can import them into scope Aug 17 16:32:29.516 INFO kablam! | Aug 17 16:32:29.516 INFO kablam! 3 | use libc::ENOTSUP; Aug 17 16:32:29.516 INFO kablam! | Aug 17 16:32:29.516 INFO kablam! 3 | use nanomsg_sys::posix_consts::ENOTSUP; Aug 17 16:32:29.517 INFO kablam! | Aug 17 16:32:29.517 INFO kablam! Aug 17 16:32:29.517 INFO kablam! error[E0425]: cannot find value `ENOTSUP` in module `nanomsg_sys` Aug 17 16:32:29.517 INFO kablam! --> src/result.rs:193:57 Aug 17 16:32:29.517 INFO kablam! | Aug 17 16:32:29.517 INFO kablam! 193 | assert_convert_error_code_to_error(nanomsg_sys::ENOTSUP, Error::OperationNotSupported); Aug 17 16:32:29.517 INFO kablam! | ^^^^^^^ not found in `nanomsg_sys` Aug 17 16:32:29.517 INFO kablam! help: possible candidates are found in other modules, you can import them into scope Aug 17 16:32:29.517 INFO kablam! | Aug 17 16:32:29.517 INFO kablam! 180 | use libc::ENOTSUP; Aug 17 16:32:29.517 INFO kablam! | Aug 17 16:32:29.517 INFO kablam! 180 | use nanomsg_sys::posix_consts::ENOTSUP; Aug 17 16:32:29.517 INFO kablam! | Aug 17 16:32:29.517 INFO kablam! Aug 17 16:32:30.338 INFO kablam! error: aborting due to 2 previous errors Aug 17 16:32:30.338 INFO kablam! Aug 17 16:32:30.338 INFO kablam! Some errors occurred: E0425, E0531. Aug 17 16:32:30.338 INFO kablam! For more information about an error, try `rustc --explain E0425`. Aug 17 16:32:30.367 INFO kablam! error: Could not compile `nanomsg`. Aug 17 16:32:30.368 INFO kablam! warning: build failed, waiting for other jobs to finish... Aug 17 16:32:30.900 INFO kablam! error: aborting due to 3 previous errors Aug 17 16:32:30.901 INFO kablam! Aug 17 16:32:30.901 INFO kablam! Some errors occurred: E0425, E0531. Aug 17 16:32:30.901 INFO kablam! For more information about an error, try `rustc --explain E0425`. Aug 17 16:32:30.912 INFO kablam! error: Could not compile `nanomsg`. Aug 17 16:32:30.912 INFO kablam! Aug 17 16:32:30.912 INFO kablam! To learn more, run the command again with --verbose. Aug 17 16:32:30.914 INFO kablam! su: No module specific data is present Aug 17 16:32:31.458 INFO running `"docker" "rm" "-f" "016b1d64be1079e47ed69aab133983e9737582c0dbaf1ffe3c83e7464c81551d"` Aug 17 16:32:31.612 INFO blam! 016b1d64be1079e47ed69aab133983e9737582c0dbaf1ffe3c83e7464c81551d