Aug 30 18:39:13.057 INFO checking entity_rust-0.0.8 against try#bc5a74802bb3ffc82f51ef04bca58d64220124c4 for pr-53699 Aug 30 18:39:13.057 INFO running: cargo +bc5a74802bb3ffc82f51ef04bca58d64220124c4-alt check --frozen --all --all-targets Aug 30 18:39:13.057 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-0/pr-53699/try#bc5a74802bb3ffc82f51ef04bca58d64220124c4:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53699/worker-0/try#bc5a74802bb3ffc82f51ef04bca58d64220124c4:/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 +bc5a74802bb3ffc82f51ef04bca58d64220124c4-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Aug 30 18:39:13.253 INFO blam! 2fb3583c46da70b1f78826bf4ad99ee2b9de067cb9d61c0dd9c664a70a4dd4a2 Aug 30 18:39:13.255 INFO running `"docker" "start" "-a" "2fb3583c46da70b1f78826bf4ad99ee2b9de067cb9d61c0dd9c664a70a4dd4a2"` Aug 30 18:39:13.875 INFO kablam! Compiling poison v0.1.0 Aug 30 18:39:13.878 INFO kablam! Compiling uuid v0.6.5 Aug 30 18:39:14.803 INFO kablam! Checking shared-mutex v0.3.1 Aug 30 18:39:16.439 INFO kablam! Checking entity_rust v0.0.8 (file:///source) Aug 30 18:39:18.037 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Aug 30 18:39:18.037 INFO kablam! --> src/lib.rs:1:12 Aug 30 18:39:18.037 INFO kablam! | Aug 30 18:39:18.037 INFO kablam! 1 | #![feature(type_macros)] Aug 30 18:39:18.037 INFO kablam! | ^^^^^^^^^^^ Aug 30 18:39:18.037 INFO kablam! | Aug 30 18:39:18.037 INFO kablam! = note: #[warn(stable_features)] on by default Aug 30 18:39:18.037 INFO kablam! Aug 30 18:39:18.216 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Aug 30 18:39:18.216 INFO kablam! --> src/lib.rs:1:12 Aug 30 18:39:18.216 INFO kablam! | Aug 30 18:39:18.216 INFO kablam! 1 | #![feature(type_macros)] Aug 30 18:39:18.216 INFO kablam! | ^^^^^^^^^^^ Aug 30 18:39:18.216 INFO kablam! | Aug 30 18:39:18.216 INFO kablam! = note: #[warn(stable_features)] on by default Aug 30 18:39:18.216 INFO kablam! Aug 30 18:39:18.538 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Aug 30 18:39:18.538 INFO kablam! --> src/lib.rs:1:12 Aug 30 18:39:18.538 INFO kablam! | Aug 30 18:39:18.538 INFO kablam! 1 | #![feature(type_macros)] Aug 30 18:39:18.538 INFO kablam! | ^^^^^^^^^^^ Aug 30 18:39:18.538 INFO kablam! | Aug 30 18:39:18.538 INFO kablam! = note: #[warn(stable_features)] on by default Aug 30 18:39:18.538 INFO kablam! Aug 30 18:39:22.475 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Aug 30 18:39:22.475 INFO kablam! --> tests/components.rs:7:1 Aug 30 18:39:22.475 INFO kablam! | Aug 30 18:39:22.475 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Aug 30 18:39:22.475 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:39:22.475 INFO kablam! | Aug 30 18:39:22.475 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:22.475 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:22.475 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:39:22.475 INFO kablam! --> tests/components.rs:7:1 Aug 30 18:39:22.475 INFO kablam! | Aug 30 18:39:22.475 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Aug 30 18:39:22.475 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:39:22.475 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) Aug 30 18:39:22.475 INFO kablam! Aug 30 18:39:22.475 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Aug 30 18:39:22.475 INFO kablam! --> tests/components.rs:7:1 Aug 30 18:39:22.476 INFO kablam! | Aug 30 18:39:22.476 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Aug 30 18:39:22.476 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Aug 30 18:39:22.476 INFO kablam! | Aug 30 18:39:22.476 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:39:22.476 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:39:22.476 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:39:22.476 INFO kablam! --> tests/components.rs:7:1 Aug 30 18:39:22.476 INFO kablam! | Aug 30 18:39:22.476 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Aug 30 18:39:22.476 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:39:22.476 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) Aug 30 18:39:22.476 INFO kablam! Aug 30 18:39:22.529 INFO kablam! error: aborting due to 2 previous errors Aug 30 18:39:22.529 INFO kablam! Aug 30 18:39:22.529 INFO kablam! For more information about this error, try `rustc --explain E0053`. Aug 30 18:39:22.550 INFO kablam! error: Could not compile `entity_rust`. Aug 30 18:39:22.557 INFO kablam! warning: build failed, waiting for other jobs to finish... Aug 30 18:39:23.132 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Aug 30 18:39:23.132 INFO kablam! --> tests/events.rs:8:1 Aug 30 18:39:23.132 INFO kablam! | Aug 30 18:39:23.132 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Aug 30 18:39:23.132 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:39:23.133 INFO kablam! | Aug 30 18:39:23.133 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.133 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.133 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:39:23.133 INFO kablam! --> tests/events.rs:8:1 Aug 30 18:39:23.133 INFO kablam! | Aug 30 18:39:23.133 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Aug 30 18:39:23.133 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:39:23.133 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) Aug 30 18:39:23.133 INFO kablam! Aug 30 18:39:23.144 INFO kablam! error: aborting due to previous error Aug 30 18:39:23.144 INFO kablam! Aug 30 18:39:23.145 INFO kablam! For more information about this error, try `rustc --explain E0053`. Aug 30 18:39:23.154 INFO kablam! error: Could not compile `entity_rust`. Aug 30 18:39:23.154 INFO kablam! warning: build failed, waiting for other jobs to finish... Aug 30 18:39:23.252 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Aug 30 18:39:23.252 INFO kablam! --> tests/lib.rs:16:1 Aug 30 18:39:23.252 INFO kablam! | Aug 30 18:39:23.252 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Aug 30 18:39:23.252 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:39:23.252 INFO kablam! | Aug 30 18:39:23.252 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.252 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.252 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:39:23.252 INFO kablam! --> tests/lib.rs:16:1 Aug 30 18:39:23.252 INFO kablam! | Aug 30 18:39:23.252 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Aug 30 18:39:23.253 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:39:23.253 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) Aug 30 18:39:23.253 INFO kablam! Aug 30 18:39:23.261 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Aug 30 18:39:23.261 INFO kablam! --> tests/lib.rs:18:1 Aug 30 18:39:23.261 INFO kablam! | Aug 30 18:39:23.261 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Aug 30 18:39:23.261 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:39:23.261 INFO kablam! | Aug 30 18:39:23.261 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.262 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.262 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:39:23.262 INFO kablam! --> tests/lib.rs:18:1 Aug 30 18:39:23.262 INFO kablam! | Aug 30 18:39:23.262 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Aug 30 18:39:23.262 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:39:23.262 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) Aug 30 18:39:23.262 INFO kablam! Aug 30 18:39:23.262 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Aug 30 18:39:23.262 INFO kablam! --> tests/lib.rs:18:1 Aug 30 18:39:23.262 INFO kablam! | Aug 30 18:39:23.262 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Aug 30 18:39:23.262 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Aug 30 18:39:23.262 INFO kablam! | Aug 30 18:39:23.262 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:39:23.262 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:39:23.262 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:39:23.262 INFO kablam! --> tests/lib.rs:18:1 Aug 30 18:39:23.262 INFO kablam! | Aug 30 18:39:23.262 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Aug 30 18:39:23.262 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:39:23.262 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) Aug 30 18:39:23.262 INFO kablam! Aug 30 18:39:23.276 INFO kablam! error: aborting due to 3 previous errors Aug 30 18:39:23.276 INFO kablam! Aug 30 18:39:23.276 INFO kablam! For more information about this error, try `rustc --explain E0053`. Aug 30 18:39:23.285 INFO kablam! error: Could not compile `entity_rust`. Aug 30 18:39:23.285 INFO kablam! warning: build failed, waiting for other jobs to finish... Aug 30 18:39:23.441 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Aug 30 18:39:23.441 INFO kablam! --> tests/systems.rs:10:1 Aug 30 18:39:23.441 INFO kablam! | Aug 30 18:39:23.441 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Aug 30 18:39:23.441 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:39:23.441 INFO kablam! | Aug 30 18:39:23.441 INFO kablam! = note: expected type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.441 INFO kablam! found type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.441 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:39:23.441 INFO kablam! --> tests/systems.rs:10:1 Aug 30 18:39:23.441 INFO kablam! | Aug 30 18:39:23.441 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Aug 30 18:39:23.441 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:39:23.441 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) Aug 30 18:39:23.441 INFO kablam! Aug 30 18:39:23.447 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Aug 30 18:39:23.447 INFO kablam! --> tests/systems.rs:11:1 Aug 30 18:39:23.447 INFO kablam! | Aug 30 18:39:23.447 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Aug 30 18:39:23.447 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:39:23.447 INFO kablam! | Aug 30 18:39:23.447 INFO kablam! = note: expected type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.447 INFO kablam! found type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.447 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:39:23.447 INFO kablam! --> tests/systems.rs:11:1 Aug 30 18:39:23.447 INFO kablam! | Aug 30 18:39:23.447 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Aug 30 18:39:23.447 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:39:23.447 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) Aug 30 18:39:23.447 INFO kablam! Aug 30 18:39:23.450 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Aug 30 18:39:23.450 INFO kablam! --> tests/systems.rs:17:2 Aug 30 18:39:23.450 INFO kablam! | Aug 30 18:39:23.450 INFO kablam! 17 | component! { position, Aug 30 18:39:23.450 INFO kablam! | _____^ Aug 30 18:39:23.450 INFO kablam! 18 | | x: i64, Aug 30 18:39:23.450 INFO kablam! 19 | | y: i64 Aug 30 18:39:23.450 INFO kablam! 20 | | } Aug 30 18:39:23.450 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:39:23.450 INFO kablam! | Aug 30 18:39:23.450 INFO kablam! = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.450 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:39:23.450 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:39:23.450 INFO kablam! --> tests/systems.rs:17:2 Aug 30 18:39:23.450 INFO kablam! | Aug 30 18:39:23.450 INFO kablam! 17 | component! { position, Aug 30 18:39:23.450 INFO kablam! | _____^ Aug 30 18:39:23.450 INFO kablam! 18 | | x: i64, Aug 30 18:39:23.450 INFO kablam! 19 | | y: i64 Aug 30 18:39:23.451 INFO kablam! 20 | | } Aug 30 18:39:23.451 INFO kablam! | |_____^ Aug 30 18:39:23.451 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) Aug 30 18:39:23.451 INFO kablam! Aug 30 18:39:23.451 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Aug 30 18:39:23.451 INFO kablam! --> tests/systems.rs:17:2 Aug 30 18:39:23.451 INFO kablam! | Aug 30 18:39:23.451 INFO kablam! 17 | component! { position, Aug 30 18:39:23.451 INFO kablam! | _____^ Aug 30 18:39:23.451 INFO kablam! 18 | | x: i64, Aug 30 18:39:23.451 INFO kablam! 19 | | y: i64 Aug 30 18:39:23.451 INFO kablam! 20 | | } Aug 30 18:39:23.451 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Aug 30 18:39:23.451 INFO kablam! | Aug 30 18:39:23.451 INFO kablam! = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:39:23.451 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:39:23.451 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:39:23.451 INFO kablam! --> tests/systems.rs:17:2 Aug 30 18:39:23.451 INFO kablam! | Aug 30 18:39:23.451 INFO kablam! 17 | component! { position, Aug 30 18:39:23.451 INFO kablam! | _____^ Aug 30 18:39:23.451 INFO kablam! 18 | | x: i64, Aug 30 18:39:23.451 INFO kablam! 19 | | y: i64 Aug 30 18:39:23.451 INFO kablam! 20 | | } Aug 30 18:39:23.451 INFO kablam! | |_____^ Aug 30 18:39:23.451 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) Aug 30 18:39:23.451 INFO kablam! Aug 30 18:39:23.464 INFO kablam! error: aborting due to 4 previous errors Aug 30 18:39:23.464 INFO kablam! Aug 30 18:39:23.464 INFO kablam! For more information about this error, try `rustc --explain E0053`. Aug 30 18:39:23.473 INFO kablam! error: Could not compile `entity_rust`. Aug 30 18:39:23.473 INFO kablam! warning: build failed, waiting for other jobs to finish... Aug 30 18:39:23.527 INFO kablam! error: build failed Aug 30 18:39:23.529 INFO kablam! su: No module specific data is present Aug 30 18:39:24.003 INFO running `"docker" "rm" "-f" "2fb3583c46da70b1f78826bf4ad99ee2b9de067cb9d61c0dd9c664a70a4dd4a2"` Aug 30 18:39:24.105 INFO blam! 2fb3583c46da70b1f78826bf4ad99ee2b9de067cb9d61c0dd9c664a70a4dd4a2