Nov 03 02:46:34.306 INFO checking rusoto_config-0.34.0 against try#dc8b02d6f1e93f212fc39844ea688b634b4a03c7 for pr-55517 Nov 03 02:46:34.307 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55517/worker-1/try#dc8b02d6f1e93f212fc39844ea688b634b4a03c7:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55517/try#dc8b02d6f1e93f212fc39844ea688b634b4a03c7:/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 +dc8b02d6f1e93f212fc39844ea688b634b4a03c7-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 03 02:46:34.704 INFO blam! 7dcd0f8394b0b85c116c1ae453cd55884fb61af2852f84c69566cfd545527ac8 Nov 03 02:46:34.720 INFO running `"docker" "start" "-a" "7dcd0f8394b0b85c116c1ae453cd55884fb61af2852f84c69566cfd545527ac8"` Nov 03 02:46:35.764 INFO kablam! usermod: no changes Nov 03 02:46:36.025 INFO kablam! Checking rusoto_core v0.35.0 Nov 03 02:46:36.026 INFO kablam! Checking rusoto_config v0.34.0 (/source) Nov 03 02:46:44.832 INFO kablam! error[E0432]: unresolved import `tls` Nov 03 02:46:44.832 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/rusoto_core-0.35.0/src/request.rs:28:5 Nov 03 02:46:44.832 INFO kablam! | Nov 03 02:46:44.832 INFO kablam! 28 | use tls::HttpsConnector; Nov 03 02:46:44.832 INFO kablam! | ^^^ Maybe a missing `extern crate tls;`? Nov 03 02:46:44.832 INFO kablam! Nov 03 02:46:44.868 INFO kablam! error[E0425]: cannot find value `connector` in this scope Nov 03 02:46:44.868 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/rusoto_core-0.35.0/src/request.rs:319:33 Nov 03 02:46:44.868 INFO kablam! | Nov 03 02:46:44.868 INFO kablam! 319 | Ok(Self::from_connector(connector)) Nov 03 02:46:44.868 INFO kablam! | ^^^^^^^^^ not found in this scope Nov 03 02:46:44.868 INFO kablam! Nov 03 02:46:45.340 INFO kablam! error[E0599]: no method named `lock` found for type `client::SHARED_CLIENT` in the current scope Nov 03 02:46:45.340 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/rusoto_core-0.35.0/src/client.rs:24:38 Nov 03 02:46:45.340 INFO kablam! | Nov 03 02:46:45.340 INFO kablam! 11 | / lazy_static! { Nov 03 02:46:45.340 INFO kablam! 12 | | static ref SHARED_CLIENT: Mutex>> = Nov 03 02:46:45.340 INFO kablam! 13 | | Mutex::new(Weak::new()); Nov 03 02:46:45.340 INFO kablam! 14 | | } Nov 03 02:46:45.340 INFO kablam! | |_- method `lock` not found for this Nov 03 02:46:45.340 INFO kablam! ... Nov 03 02:46:45.340 INFO kablam! 24 | let mut lock = SHARED_CLIENT.lock().unwrap(); Nov 03 02:46:45.340 INFO kablam! | ^^^^ Nov 03 02:46:45.340 INFO kablam! | Nov 03 02:46:45.340 INFO kablam! = help: items from traits can only be used if the trait is implemented and in scope Nov 03 02:46:45.340 INFO kablam! = note: the following trait defines an item `lock`, perhaps you need to implement it: Nov 03 02:46:45.340 INFO kablam! candidate #1: `lock_api::mutex::RawMutex` Nov 03 02:46:45.340 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 03 02:46:45.340 INFO kablam! Nov 03 02:46:45.712 INFO kablam! error: aborting due to 3 previous errors Nov 03 02:46:45.712 INFO kablam! Nov 03 02:46:45.712 INFO kablam! Some errors occurred: E0425, E0432, E0599. Nov 03 02:46:45.712 INFO kablam! For more information about an error, try `rustc --explain E0425`. Nov 03 02:46:45.732 INFO kablam! error: Could not compile `rusoto_core`. Nov 03 02:46:45.732 INFO kablam! warning: build failed, waiting for other jobs to finish... Nov 03 02:46:51.217 INFO kablam! error: build failed Nov 03 02:46:51.218 INFO kablam! su: No module specific data is present Nov 03 02:46:51.636 INFO running `"docker" "rm" "-f" "7dcd0f8394b0b85c116c1ae453cd55884fb61af2852f84c69566cfd545527ac8"` Nov 03 02:46:51.925 INFO blam! 7dcd0f8394b0b85c116c1ae453cd55884fb61af2852f84c69566cfd545527ac8