Sep 02 18:36:23.198 INFO checking carrier-0.2.0 against master#1114ab684fbad001c4e580326d8eb4d8c4e917d3 for pr-53851 Sep 02 18:36:23.198 INFO running: cargo +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets Sep 02 18:36:23.198 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-0/pr-53851/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53851/worker-0/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/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 +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Sep 02 18:36:23.445 INFO blam! 4239f0c4ad36f6f2cde1a155a832bb8dff0e67c52c4cc555738b585657ce7f86 Sep 02 18:36:23.448 INFO running `"docker" "start" "-a" "4239f0c4ad36f6f2cde1a155a832bb8dff0e67c52c4cc555738b585657ce7f86"` Sep 02 18:36:24.632 INFO kablam! Compiling subtle v0.7.0 Sep 02 18:36:24.662 INFO kablam! Checking bs58 v0.2.1 Sep 02 18:36:24.687 INFO kablam! Compiling rand v0.5.5 Sep 02 18:36:24.732 INFO kablam! Compiling bytes v0.4.9 Sep 02 18:36:24.734 INFO kablam! Checking parking_lot_core v0.3.0 Sep 02 18:36:24.734 INFO kablam! Checking tokio-io v0.1.8 Sep 02 18:36:24.735 INFO kablam! Checking prost v0.4.0 Sep 02 18:36:24.735 INFO kablam! Compiling snow v0.4.0-alpha2 Sep 02 18:36:28.055 INFO kablam! Checking hpack v0.3.0 Sep 02 18:36:29.278 INFO kablam! Checking tokio-threadpool v0.1.6 Sep 02 18:36:32.663 INFO kablam! Checking parking_lot v0.6.4 Sep 02 18:36:35.858 INFO kablam! Checking tokio-codec v0.1.0 Sep 02 18:36:39.487 INFO kablam! Checking tokio-reactor v0.1.5 Sep 02 18:36:40.643 INFO kablam! Checking tokio-fs v0.1.3 Sep 02 18:36:43.682 INFO kablam! Compiling prost-types v0.4.0 Sep 02 18:36:45.559 INFO kablam! Compiling curve25519-dalek v0.19.0 Sep 02 18:36:47.011 INFO kablam! Checking tokio-uds v0.2.1 Sep 02 18:36:47.011 INFO kablam! Checking tokio-udp v0.1.2 Sep 02 18:36:47.011 INFO kablam! Checking tokio-tcp v0.1.1 Sep 02 18:36:55.141 INFO kablam! Checking tokio v0.1.8 Sep 02 18:37:01.583 INFO kablam! Compiling prost-build v0.4.0 Sep 02 18:37:01.816 INFO kablam! Checking x25519-dalek v0.3.0 Sep 02 18:37:01.819 INFO kablam! Checking ed25519-dalek v0.8.0 Sep 02 18:37:09.384 INFO kablam! Compiling carrier v0.2.0 (file:///source) Sep 02 18:37:24.559 INFO kablam! error[E0369]: binary operation `==` cannot be applied to type `std::result::Result` Sep 02 18:37:24.559 INFO kablam! --> src/identity.rs:337:5 Sep 02 18:37:24.559 INFO kablam! | Sep 02 18:37:24.559 INFO kablam! 337 | assert_eq!(client_identity.verify(b"goes on postcards", text, &signature), Ok(true)); Sep 02 18:37:24.559 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 02 18:37:24.560 INFO kablam! | Sep 02 18:37:24.560 INFO kablam! = note: an implementation of `std::cmp::PartialEq` might be missing for `std::result::Result` Sep 02 18:37:24.560 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) Sep 02 18:37:24.560 INFO kablam! Sep 02 18:37:24.562 INFO kablam! error[E0369]: binary operation `==` cannot be applied to type `std::result::Result` Sep 02 18:37:24.562 INFO kablam! --> src/identity.rs:338:5 Sep 02 18:37:24.562 INFO kablam! | Sep 02 18:37:24.562 INFO kablam! 338 | / assert_eq!( Sep 02 18:37:24.562 INFO kablam! 339 | | client_identity.verify(b"does not go on postcards", text, &signature), Sep 02 18:37:24.562 INFO kablam! 340 | | Ok(false) Sep 02 18:37:24.562 INFO kablam! 341 | | ); Sep 02 18:37:24.562 INFO kablam! | |______^ Sep 02 18:37:24.562 INFO kablam! | Sep 02 18:37:24.563 INFO kablam! = note: an implementation of `std::cmp::PartialEq` might be missing for `std::result::Result` Sep 02 18:37:24.563 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) Sep 02 18:37:24.563 INFO kablam! Sep 02 18:37:24.569 INFO kablam! error[E0369]: binary operation `==` cannot be applied to type `std::result::Result` Sep 02 18:37:24.569 INFO kablam! --> src/identity.rs:352:5 Sep 02 18:37:24.569 INFO kablam! | Sep 02 18:37:24.569 INFO kablam! 352 | / assert_ne!( Sep 02 18:37:24.569 INFO kablam! 353 | | client_identity.verify(b"goes on postcards", text, &Signature(signature_invalid)), Sep 02 18:37:24.569 INFO kablam! 354 | | Ok(true) Sep 02 18:37:24.569 INFO kablam! 355 | | ); Sep 02 18:37:24.569 INFO kablam! | |______^ Sep 02 18:37:24.569 INFO kablam! | Sep 02 18:37:24.569 INFO kablam! = note: an implementation of `std::cmp::PartialEq` might be missing for `std::result::Result` Sep 02 18:37:24.569 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) Sep 02 18:37:24.569 INFO kablam! Sep 02 18:37:24.573 INFO kablam! error[E0369]: binary operation `==` cannot be applied to type `std::result::Result` Sep 02 18:37:24.573 INFO kablam! --> src/identity.rs:359:5 Sep 02 18:37:24.573 INFO kablam! | Sep 02 18:37:24.573 INFO kablam! 359 | / assert_ne!( Sep 02 18:37:24.573 INFO kablam! 360 | | client_identity.verify(b"goes on postcards", &text_invalid, &signature), Sep 02 18:37:24.573 INFO kablam! 361 | | Ok(true) Sep 02 18:37:24.573 INFO kablam! 362 | | ); Sep 02 18:37:24.573 INFO kablam! | |______^ Sep 02 18:37:24.573 INFO kablam! | Sep 02 18:37:24.573 INFO kablam! = note: an implementation of `std::cmp::PartialEq` might be missing for `std::result::Result` Sep 02 18:37:24.573 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) Sep 02 18:37:24.573 INFO kablam! Sep 02 18:37:24.874 INFO kablam! error[E0063]: missing field `stream` in initializer of `packet::Frame` Sep 02 18:37:24.874 INFO kablam! --> src/packet.rs:209:17 Sep 02 18:37:24.874 INFO kablam! | Sep 02 18:37:24.874 INFO kablam! 209 | let frame = Frame::Stream { Sep 02 18:37:24.874 INFO kablam! | ^^^^^^^^^^^^^ missing `stream` Sep 02 18:37:24.874 INFO kablam! Sep 02 18:37:24.895 INFO kablam! error[E0027]: pattern does not mention field `stream` Sep 02 18:37:24.895 INFO kablam! --> src/packet.rs:246:12 Sep 02 18:37:24.895 INFO kablam! | Sep 02 18:37:24.895 INFO kablam! 246 | if let Frame::Stream { order, ref payload } = frames[0] { Sep 02 18:37:24.895 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ missing field `stream` Sep 02 18:37:24.895 INFO kablam! Sep 02 18:37:24.995 INFO kablam! error[E0223]: ambiguous associated type Sep 02 18:37:24.995 INFO kablam! --> src/recovery.rs:528:21 Sep 02 18:37:24.995 INFO kablam! | Sep 02 18:37:24.995 INFO kablam! 528 | let frame = Frame::Message { Sep 02 18:37:24.995 INFO kablam! | ^^^^^^^^^^^^^^ ambiguous associated type Sep 02 18:37:24.995 INFO kablam! | Sep 02 18:37:24.996 INFO kablam! = note: specify the type using the syntax `::Message` Sep 02 18:37:24.996 INFO kablam! Sep 02 18:37:25.010 INFO kablam! error[E0223]: ambiguous associated type Sep 02 18:37:25.010 INFO kablam! --> src/recovery.rs:557:21 Sep 02 18:37:25.010 INFO kablam! | Sep 02 18:37:25.010 INFO kablam! 557 | let frame = Frame::Message { Sep 02 18:37:25.010 INFO kablam! | ^^^^^^^^^^^^^^ ambiguous associated type Sep 02 18:37:25.010 INFO kablam! | Sep 02 18:37:25.010 INFO kablam! = note: specify the type using the syntax `::Message` Sep 02 18:37:25.010 INFO kablam! Sep 02 18:37:25.079 INFO kablam! error[E0223]: ambiguous associated type Sep 02 18:37:25.079 INFO kablam! --> src/recovery.rs:676:21 Sep 02 18:37:25.079 INFO kablam! | Sep 02 18:37:25.079 INFO kablam! 676 | let frame = Frame::Message { Sep 02 18:37:25.079 INFO kablam! | ^^^^^^^^^^^^^^ ambiguous associated type Sep 02 18:37:25.079 INFO kablam! | Sep 02 18:37:25.079 INFO kablam! = note: specify the type using the syntax `::Message` Sep 02 18:37:25.079 INFO kablam! Sep 02 18:37:25.246 INFO kablam! error[E0223]: ambiguous associated type Sep 02 18:37:25.246 INFO kablam! --> src/stream.rs:83:17 Sep 02 18:37:25.246 INFO kablam! | Sep 02 18:37:25.246 INFO kablam! 83 | st.push(Frame::Message { Sep 02 18:37:25.246 INFO kablam! | ^^^^^^^^^^^^^^ ambiguous associated type Sep 02 18:37:25.246 INFO kablam! | Sep 02 18:37:25.246 INFO kablam! = note: specify the type using the syntax `::Message` Sep 02 18:37:25.247 INFO kablam! Sep 02 18:37:25.247 INFO kablam! error[E0223]: ambiguous associated type Sep 02 18:37:25.247 INFO kablam! --> src/stream.rs:89:17 Sep 02 18:37:25.248 INFO kablam! | Sep 02 18:37:25.248 INFO kablam! 89 | st.push(Frame::Message { Sep 02 18:37:25.248 INFO kablam! | ^^^^^^^^^^^^^^ ambiguous associated type Sep 02 18:37:25.248 INFO kablam! | Sep 02 18:37:25.248 INFO kablam! = note: specify the type using the syntax `::Message` Sep 02 18:37:25.248 INFO kablam! Sep 02 18:37:25.249 INFO kablam! error[E0223]: ambiguous associated type Sep 02 18:37:25.249 INFO kablam! --> src/stream.rs:100:17 Sep 02 18:37:25.249 INFO kablam! | Sep 02 18:37:25.249 INFO kablam! 100 | st.push(Frame::Message { Sep 02 18:37:25.249 INFO kablam! | ^^^^^^^^^^^^^^ ambiguous associated type Sep 02 18:37:25.249 INFO kablam! | Sep 02 18:37:25.249 INFO kablam! = note: specify the type using the syntax `::Message` Sep 02 18:37:25.249 INFO kablam! Sep 02 18:37:25.250 INFO kablam! error[E0223]: ambiguous associated type Sep 02 18:37:25.250 INFO kablam! --> src/stream.rs:111:17 Sep 02 18:37:25.250 INFO kablam! | Sep 02 18:37:25.250 INFO kablam! 111 | st.push(Frame::Message { Sep 02 18:37:25.250 INFO kablam! | ^^^^^^^^^^^^^^ ambiguous associated type Sep 02 18:37:25.251 INFO kablam! | Sep 02 18:37:25.251 INFO kablam! = note: specify the type using the syntax `::Message` Sep 02 18:37:25.251 INFO kablam! Sep 02 18:37:25.252 INFO kablam! error[E0223]: ambiguous associated type Sep 02 18:37:25.252 INFO kablam! --> src/stream.rs:120:13 Sep 02 18:37:25.252 INFO kablam! | Sep 02 18:37:25.252 INFO kablam! 120 | Frame::Message { Sep 02 18:37:25.252 INFO kablam! | ^^^^^^^^^^^^^^ ambiguous associated type Sep 02 18:37:25.252 INFO kablam! | Sep 02 18:37:25.252 INFO kablam! = note: specify the type using the syntax `::Message` Sep 02 18:37:25.252 INFO kablam! Sep 02 18:37:25.257 INFO kablam! error[E0223]: ambiguous associated type Sep 02 18:37:25.257 INFO kablam! --> src/stream.rs:138:17 Sep 02 18:37:25.257 INFO kablam! | Sep 02 18:37:25.257 INFO kablam! 138 | st.push(Frame::Message { Sep 02 18:37:25.257 INFO kablam! | ^^^^^^^^^^^^^^ ambiguous associated type Sep 02 18:37:25.257 INFO kablam! | Sep 02 18:37:25.257 INFO kablam! = note: specify the type using the syntax `::Message` Sep 02 18:37:25.257 INFO kablam! Sep 02 18:37:25.258 INFO kablam! error[E0223]: ambiguous associated type Sep 02 18:37:25.258 INFO kablam! --> src/stream.rs:147:13 Sep 02 18:37:25.258 INFO kablam! | Sep 02 18:37:25.258 INFO kablam! 147 | Frame::Message { Sep 02 18:37:25.259 INFO kablam! | ^^^^^^^^^^^^^^ ambiguous associated type Sep 02 18:37:25.259 INFO kablam! | Sep 02 18:37:25.259 INFO kablam! = note: specify the type using the syntax `::Message` Sep 02 18:37:25.259 INFO kablam! Sep 02 18:37:25.712 INFO kablam! error: aborting due to 16 previous errors Sep 02 18:37:25.712 INFO kablam! Sep 02 18:37:25.712 INFO kablam! Some errors occurred: E0027, E0063, E0223, E0369. Sep 02 18:37:25.713 INFO kablam! For more information about an error, try `rustc --explain E0027`. Sep 02 18:37:25.727 INFO kablam! error: Could not compile `carrier`. Sep 02 18:37:25.727 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 02 18:37:28.514 INFO kablam! warning: field is never used: `debug_id` Sep 02 18:37:28.514 INFO kablam! --> src/noise.rs:34:5 Sep 02 18:37:28.515 INFO kablam! | Sep 02 18:37:28.515 INFO kablam! 34 | pub(crate) debug_id: String, Sep 02 18:37:28.515 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 02 18:37:28.515 INFO kablam! | Sep 02 18:37:28.515 INFO kablam! = note: #[warn(dead_code)] on by default Sep 02 18:37:28.515 INFO kablam! Sep 02 18:37:28.515 INFO kablam! warning: variant is never constructed: `ResponderEof` Sep 02 18:37:28.515 INFO kablam! --> /target/debug/build/carrier-2f4fa45130c5a647/out/ox.axiom.v1.rs:22:149 Sep 02 18:37:28.515 INFO kablam! | Sep 02 18:37:28.515 INFO kablam! 22 | # [ fail ( display = "unexpected EOF waiting for headers" ) ] HeaderEof , # [ fail ( display = "unexpected EOF waiting for response rpc object" ) ] ResponderEof , # [ fail ( display = "unexpected EOF waiting for callers rpc object" ) ] CallerEof , # [ fail ( display = "remote error : {:?} : {:?}" , status , error ) ] RemoteError { Sep 02 18:37:28.515 INFO kablam! | ^^^^^^^^^^^^ Sep 02 18:37:28.516 INFO kablam! Sep 02 18:37:28.516 INFO kablam! warning: variant is never constructed: `CallerEof` Sep 02 18:37:28.516 INFO kablam! --> /target/debug/build/carrier-2f4fa45130c5a647/out/ox.axiom.v1.rs:22:237 Sep 02 18:37:28.516 INFO kablam! | Sep 02 18:37:28.516 INFO kablam! 22 | # [ fail ( display = "unexpected EOF waiting for headers" ) ] HeaderEof , # [ fail ( display = "unexpected EOF waiting for response rpc object" ) ] ResponderEof , # [ fail ( display = "unexpected EOF waiting for callers rpc object" ) ] CallerEof , # [ fail ( display = "remote error : {:?} : {:?}" , status , error ) ] RemoteError { Sep 02 18:37:28.516 INFO kablam! | ^^^^^^^^^ Sep 02 18:37:28.516 INFO kablam! Sep 02 18:37:28.720 INFO kablam! error: build failed Sep 02 18:37:28.722 INFO kablam! su: No module specific data is present Sep 02 18:37:29.135 INFO running `"docker" "rm" "-f" "4239f0c4ad36f6f2cde1a155a832bb8dff0e67c52c4cc555738b585657ce7f86"` Sep 02 18:37:29.269 INFO blam! 4239f0c4ad36f6f2cde1a155a832bb8dff0e67c52c4cc555738b585657ce7f86