Jul 12 03:44:55.574 INFO checking nanomsg-0.5.0 against try#d39a6f7eddafd45dcc60e99001b8cd08c2bd3255 for pr-52234 Jul 12 03:44:55.574 INFO running: cargo +d39a6f7eddafd45dcc60e99001b8cd08c2bd3255-alt check --frozen --all --all-targets Jul 12 03:44:55.574 INFO creating container for: cargo +d39a6f7eddafd45dcc60e99001b8cd08c2bd3255-alt check --frozen --all --all-targets Jul 12 03:44:55.575 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-3/pr-52234/try#d39a6f7eddafd45dcc60e99001b8cd08c2bd3255:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-52234/worker-3/try#d39a6f7eddafd45dcc60e99001b8cd08c2bd3255:/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 +d39a6f7eddafd45dcc60e99001b8cd08c2bd3255-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "crater"` Jul 12 03:44:55.851 INFO blam! e660d9357152ff45f58f22c63d901fed907809924bf2fb0360f43a34755c464e Jul 12 03:44:55.854 INFO running `"docker" "start" "-a" "e660d9357152ff45f58f22c63d901fed907809924bf2fb0360f43a34755c464e"` Jul 12 03:44:57.152 INFO kablam! Compiling nanomsg-sys v0.5.0 Jul 12 03:44:58.706 INFO kablam! Checking nanomsg v0.5.0 (file:///source) Jul 12 03:44:59.412 INFO kablam! error[E0425]: cannot find value `ENOTSUP` in module `nanomsg_sys` Jul 12 03:44:59.412 INFO kablam! --> src/result.rs:19:47 Jul 12 03:44:59.412 INFO kablam! | Jul 12 03:44:59.413 INFO kablam! 19 | OperationNotSupported = nanomsg_sys::ENOTSUP as isize, Jul 12 03:44:59.413 INFO kablam! | ^^^^^^^ not found in `nanomsg_sys` Jul 12 03:44:59.413 INFO kablam! help: possible candidates are found in other modules, you can import them into scope Jul 12 03:44:59.413 INFO kablam! | Jul 12 03:44:59.413 INFO kablam! 3 | use libc::ENOTSUP; Jul 12 03:44:59.413 INFO kablam! | Jul 12 03:44:59.413 INFO kablam! 3 | use nanomsg_sys::posix_consts::ENOTSUP; Jul 12 03:44:59.413 INFO kablam! | Jul 12 03:44:59.413 INFO kablam! Jul 12 03:44:59.413 INFO kablam! error[E0531]: cannot find unit struct/variant or constant `ENOTSUP` in module `nanomsg_sys` Jul 12 03:44:59.413 INFO kablam! --> src/result.rs:61:26 Jul 12 03:44:59.413 INFO kablam! | Jul 12 03:44:59.413 INFO kablam! 61 | nanomsg_sys::ENOTSUP => Error::OperationNotSupported , Jul 12 03:44:59.413 INFO kablam! | ^^^^^^^ not found in `nanomsg_sys` Jul 12 03:44:59.413 INFO kablam! help: possible candidates are found in other modules, you can import them into scope Jul 12 03:44:59.413 INFO kablam! | Jul 12 03:44:59.413 INFO kablam! 3 | use libc::ENOTSUP; Jul 12 03:44:59.413 INFO kablam! | Jul 12 03:44:59.413 INFO kablam! 3 | use nanomsg_sys::posix_consts::ENOTSUP; Jul 12 03:44:59.413 INFO kablam! | Jul 12 03:44:59.413 INFO kablam! Jul 12 03:44:59.843 INFO kablam! error: aborting due to 2 previous errors Jul 12 03:44:59.843 INFO kablam! Jul 12 03:44:59.843 INFO kablam! Some errors occurred: E0425, E0531. Jul 12 03:44:59.843 INFO kablam! For more information about an error, try `rustc --explain E0425`. Jul 12 03:44:59.865 INFO kablam! error: Could not compile `nanomsg`. Jul 12 03:44:59.865 INFO kablam! warning: build failed, waiting for other jobs to finish... Jul 12 03:44:59.999 INFO kablam! error[E0425]: cannot find value `ENOTSUP` in module `nanomsg_sys` Jul 12 03:45:00.000 INFO kablam! --> src/result.rs:19:47 Jul 12 03:45:00.000 INFO kablam! | Jul 12 03:45:00.000 INFO kablam! 19 | OperationNotSupported = nanomsg_sys::ENOTSUP as isize, Jul 12 03:45:00.000 INFO kablam! | ^^^^^^^ not found in `nanomsg_sys` Jul 12 03:45:00.000 INFO kablam! help: possible candidates are found in other modules, you can import them into scope Jul 12 03:45:00.001 INFO kablam! | Jul 12 03:45:00.001 INFO kablam! 3 | use libc::ENOTSUP; Jul 12 03:45:00.001 INFO kablam! | Jul 12 03:45:00.001 INFO kablam! 3 | use nanomsg_sys::posix_consts::ENOTSUP; Jul 12 03:45:00.001 INFO kablam! | Jul 12 03:45:00.001 INFO kablam! Jul 12 03:45:00.001 INFO kablam! error[E0531]: cannot find unit struct/variant or constant `ENOTSUP` in module `nanomsg_sys` Jul 12 03:45:00.001 INFO kablam! --> src/result.rs:61:26 Jul 12 03:45:00.001 INFO kablam! | Jul 12 03:45:00.001 INFO kablam! 61 | nanomsg_sys::ENOTSUP => Error::OperationNotSupported , Jul 12 03:45:00.001 INFO kablam! | ^^^^^^^ not found in `nanomsg_sys` Jul 12 03:45:00.001 INFO kablam! help: possible candidates are found in other modules, you can import them into scope Jul 12 03:45:00.001 INFO kablam! | Jul 12 03:45:00.001 INFO kablam! 3 | use libc::ENOTSUP; Jul 12 03:45:00.001 INFO kablam! | Jul 12 03:45:00.001 INFO kablam! 3 | use nanomsg_sys::posix_consts::ENOTSUP; Jul 12 03:45:00.001 INFO kablam! | Jul 12 03:45:00.001 INFO kablam! Jul 12 03:45:00.001 INFO kablam! error[E0425]: cannot find value `ENOTSUP` in module `nanomsg_sys` Jul 12 03:45:00.001 INFO kablam! --> src/result.rs:193:57 Jul 12 03:45:00.001 INFO kablam! | Jul 12 03:45:00.001 INFO kablam! 193 | assert_convert_error_code_to_error(nanomsg_sys::ENOTSUP, Error::OperationNotSupported); Jul 12 03:45:00.001 INFO kablam! | ^^^^^^^ not found in `nanomsg_sys` Jul 12 03:45:00.001 INFO kablam! help: possible candidates are found in other modules, you can import them into scope Jul 12 03:45:00.001 INFO kablam! | Jul 12 03:45:00.001 INFO kablam! 180 | use libc::ENOTSUP; Jul 12 03:45:00.001 INFO kablam! | Jul 12 03:45:00.001 INFO kablam! 180 | use nanomsg_sys::posix_consts::ENOTSUP; Jul 12 03:45:00.001 INFO kablam! | Jul 12 03:45:00.001 INFO kablam! Jul 12 03:45:00.784 INFO kablam! error: aborting due to 3 previous errors Jul 12 03:45:00.784 INFO kablam! Jul 12 03:45:00.784 INFO kablam! Some errors occurred: E0425, E0531. Jul 12 03:45:00.784 INFO kablam! For more information about an error, try `rustc --explain E0425`. Jul 12 03:45:00.793 INFO kablam! error: Could not compile `nanomsg`. Jul 12 03:45:00.793 INFO kablam! Jul 12 03:45:00.793 INFO kablam! To learn more, run the command again with --verbose. Jul 12 03:45:00.796 INFO kablam! su: No module specific data is present Jul 12 03:45:01.281 INFO running `"docker" "rm" "-f" "e660d9357152ff45f58f22c63d901fed907809924bf2fb0360f43a34755c464e"` Jul 12 03:45:01.442 INFO blam! e660d9357152ff45f58f22c63d901fed907809924bf2fb0360f43a34755c464e