Nov 04 18:30:55.925 INFO checking rusoto_cloudhsm-0.34.0 against try#e740b9aa0b624fa39feb39613e76d15bdf57e594 for pr-55655 Nov 04 18:30:55.927 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55655/worker-5/try#e740b9aa0b624fa39feb39613e76d15bdf57e594:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-55655/try#e740b9aa0b624fa39feb39613e76d15bdf57e594:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +e740b9aa0b624fa39feb39613e76d15bdf57e594-alt check --frozen --all --all-targets" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"` Nov 04 18:30:56.327 INFO blam! 9e68eada83228e57acf3966d3097fec7363e2ad42b9a9a38eedefd3c5b2c674e Nov 04 18:30:56.329 INFO running `"docker" "start" "-a" "9e68eada83228e57acf3966d3097fec7363e2ad42b9a9a38eedefd3c5b2c674e"` Nov 04 18:30:57.555 INFO kablam! usermod: no changes Nov 04 18:30:57.795 INFO kablam! Checking rusoto_core v0.35.0 Nov 04 18:30:57.795 INFO kablam! Checking rusoto_cloudhsm v0.34.0 (/source) Nov 04 18:31:03.582 INFO kablam! error[E0432]: unresolved import `tls` Nov 04 18:31:03.583 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/rusoto_core-0.35.0/src/request.rs:28:5 Nov 04 18:31:03.583 INFO kablam! | Nov 04 18:31:03.583 INFO kablam! 28 | use tls::HttpsConnector; Nov 04 18:31:03.583 INFO kablam! | ^^^ Maybe a missing `extern crate tls;`? Nov 04 18:31:03.583 INFO kablam! Nov 04 18:31:03.594 INFO kablam! error[E0425]: cannot find value `connector` in this scope Nov 04 18:31:03.595 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/rusoto_core-0.35.0/src/request.rs:319:33 Nov 04 18:31:03.595 INFO kablam! | Nov 04 18:31:03.595 INFO kablam! 319 | Ok(Self::from_connector(connector)) Nov 04 18:31:03.595 INFO kablam! | ^^^^^^^^^ not found in this scope Nov 04 18:31:03.595 INFO kablam! Nov 04 18:31:03.867 INFO kablam! error[E0599]: no method named `lock` found for type `client::SHARED_CLIENT` in the current scope Nov 04 18:31:03.867 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/rusoto_core-0.35.0/src/client.rs:24:38 Nov 04 18:31:03.867 INFO kablam! | Nov 04 18:31:03.867 INFO kablam! 11 | / lazy_static! { Nov 04 18:31:03.868 INFO kablam! 12 | | static ref SHARED_CLIENT: Mutex>> = Nov 04 18:31:03.868 INFO kablam! 13 | | Mutex::new(Weak::new()); Nov 04 18:31:03.868 INFO kablam! 14 | | } Nov 04 18:31:03.868 INFO kablam! | |_- method `lock` not found for this Nov 04 18:31:03.868 INFO kablam! ... Nov 04 18:31:03.868 INFO kablam! 24 | let mut lock = SHARED_CLIENT.lock().unwrap(); Nov 04 18:31:03.869 INFO kablam! | ^^^^ Nov 04 18:31:03.869 INFO kablam! | Nov 04 18:31:03.869 INFO kablam! = help: items from traits can only be used if the trait is implemented and in scope Nov 04 18:31:03.869 INFO kablam! = note: the following trait defines an item `lock`, perhaps you need to implement it: Nov 04 18:31:03.869 INFO kablam! candidate #1: `lock_api::mutex::RawMutex` Nov 04 18:31:03.869 INFO kablam! = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info) Nov 04 18:31:03.870 INFO kablam! Nov 04 18:31:04.178 INFO kablam! error: aborting due to 3 previous errors Nov 04 18:31:04.179 INFO kablam! Nov 04 18:31:04.179 INFO kablam! Some errors occurred: E0425, E0432, E0599. Nov 04 18:31:04.179 INFO kablam! For more information about an error, try `rustc --explain E0425`. Nov 04 18:31:04.186 INFO kablam! error: Could not compile `rusoto_core`. Nov 04 18:31:04.186 INFO kablam! warning: build failed, waiting for other jobs to finish... Nov 04 18:31:06.771 INFO kablam! error: build failed Nov 04 18:31:06.775 INFO kablam! su: No module specific data is present Nov 04 18:31:07.954 INFO running `"docker" "rm" "-f" "9e68eada83228e57acf3966d3097fec7363e2ad42b9a9a38eedefd3c5b2c674e"` Nov 04 18:31:08.349 INFO blam! 9e68eada83228e57acf3966d3097fec7363e2ad42b9a9a38eedefd3c5b2c674e