Sep 02 15:20:33.139 INFO checking entity_rust-0.0.8 against master#1114ab684fbad001c4e580326d8eb4d8c4e917d3 for pr-53851 Sep 02 15:20:33.139 INFO running: cargo +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets Sep 02 15:20:33.139 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-2/pr-53851/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53851/worker-2/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 15:20:33.361 INFO blam! 940243b9d485205d890bbe10e6865238735884fa029f7fa3a3d6f65daff008e1 Sep 02 15:20:33.364 INFO running `"docker" "start" "-a" "940243b9d485205d890bbe10e6865238735884fa029f7fa3a3d6f65daff008e1"` Sep 02 15:20:34.198 INFO kablam! Compiling poison v0.1.0 Sep 02 15:20:34.207 INFO kablam! Checking uuid v0.6.5 Sep 02 15:20:35.243 INFO kablam! Compiling shared-mutex v0.3.1 Sep 02 15:20:36.621 INFO kablam! Compiling entity_rust v0.0.8 (file:///source) Sep 02 15:20:37.844 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Sep 02 15:20:37.844 INFO kablam! --> src/lib.rs:1:12 Sep 02 15:20:37.844 INFO kablam! | Sep 02 15:20:37.844 INFO kablam! 1 | #![feature(type_macros)] Sep 02 15:20:37.844 INFO kablam! | ^^^^^^^^^^^ Sep 02 15:20:37.844 INFO kablam! | Sep 02 15:20:37.844 INFO kablam! = note: #[warn(stable_features)] on by default Sep 02 15:20:37.844 INFO kablam! Sep 02 15:20:37.895 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Sep 02 15:20:37.895 INFO kablam! --> src/lib.rs:1:12 Sep 02 15:20:37.895 INFO kablam! | Sep 02 15:20:37.895 INFO kablam! 1 | #![feature(type_macros)] Sep 02 15:20:37.895 INFO kablam! | ^^^^^^^^^^^ Sep 02 15:20:37.895 INFO kablam! | Sep 02 15:20:37.895 INFO kablam! = note: #[warn(stable_features)] on by default Sep 02 15:20:37.895 INFO kablam! Sep 02 15:20:37.959 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Sep 02 15:20:37.959 INFO kablam! --> src/lib.rs:1:12 Sep 02 15:20:37.959 INFO kablam! | Sep 02 15:20:37.959 INFO kablam! 1 | #![feature(type_macros)] Sep 02 15:20:37.959 INFO kablam! | ^^^^^^^^^^^ Sep 02 15:20:37.959 INFO kablam! | Sep 02 15:20:37.959 INFO kablam! = note: #[warn(stable_features)] on by default Sep 02 15:20:37.960 INFO kablam! Sep 02 15:20:42.341 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 02 15:20:42.341 INFO kablam! --> tests/components.rs:7:1 Sep 02 15:20:42.341 INFO kablam! | Sep 02 15:20:42.341 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 02 15:20:42.341 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 02 15:20:42.341 INFO kablam! | Sep 02 15:20:42.341 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.341 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.342 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 02 15:20:42.342 INFO kablam! --> tests/components.rs:7:1 Sep 02 15:20:42.342 INFO kablam! | Sep 02 15:20:42.342 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 02 15:20:42.342 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 02 15:20:42.342 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 15:20:42.342 INFO kablam! Sep 02 15:20:42.342 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 02 15:20:42.342 INFO kablam! --> tests/components.rs:7:1 Sep 02 15:20:42.342 INFO kablam! | Sep 02 15:20:42.342 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 02 15:20:42.342 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 02 15:20:42.342 INFO kablam! | Sep 02 15:20:42.343 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 02 15:20:42.343 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 02 15:20:42.343 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 02 15:20:42.343 INFO kablam! --> tests/components.rs:7:1 Sep 02 15:20:42.343 INFO kablam! | Sep 02 15:20:42.343 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 02 15:20:42.343 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 02 15:20:42.343 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 15:20:42.343 INFO kablam! Sep 02 15:20:42.365 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 02 15:20:42.365 INFO kablam! --> tests/events.rs:8:1 Sep 02 15:20:42.365 INFO kablam! | Sep 02 15:20:42.365 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Sep 02 15:20:42.365 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 02 15:20:42.366 INFO kablam! | Sep 02 15:20:42.366 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.366 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.367 INFO kablam! error: aborting due to 2 previous errors Sep 02 15:20:42.367 INFO kablam! Sep 02 15:20:42.367 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 02 15:20:42.368 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 02 15:20:42.368 INFO kablam! --> tests/events.rs:8:1 Sep 02 15:20:42.368 INFO kablam! | Sep 02 15:20:42.368 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Sep 02 15:20:42.368 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 02 15:20:42.368 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 15:20:42.368 INFO kablam! Sep 02 15:20:42.375 INFO kablam! error: Could not compile `entity_rust`. Sep 02 15:20:42.375 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 02 15:20:42.380 INFO kablam! error: aborting due to previous error Sep 02 15:20:42.380 INFO kablam! Sep 02 15:20:42.380 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 02 15:20:42.389 INFO kablam! error: Could not compile `entity_rust`. Sep 02 15:20:42.389 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 02 15:20:42.568 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 02 15:20:42.568 INFO kablam! --> tests/lib.rs:16:1 Sep 02 15:20:42.568 INFO kablam! | Sep 02 15:20:42.568 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Sep 02 15:20:42.568 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 02 15:20:42.568 INFO kablam! | Sep 02 15:20:42.568 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.568 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.569 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 02 15:20:42.569 INFO kablam! --> tests/lib.rs:16:1 Sep 02 15:20:42.569 INFO kablam! | Sep 02 15:20:42.569 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Sep 02 15:20:42.569 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 02 15:20:42.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 15:20:42.569 INFO kablam! Sep 02 15:20:42.572 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 02 15:20:42.572 INFO kablam! --> tests/lib.rs:18:1 Sep 02 15:20:42.572 INFO kablam! | Sep 02 15:20:42.572 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 02 15:20:42.572 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 02 15:20:42.572 INFO kablam! | Sep 02 15:20:42.573 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.573 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.573 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 02 15:20:42.573 INFO kablam! --> tests/lib.rs:18:1 Sep 02 15:20:42.573 INFO kablam! | Sep 02 15:20:42.573 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 02 15:20:42.573 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 02 15:20:42.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 15:20:42.573 INFO kablam! Sep 02 15:20:42.573 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 02 15:20:42.573 INFO kablam! --> tests/lib.rs:18:1 Sep 02 15:20:42.573 INFO kablam! | Sep 02 15:20:42.573 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 02 15:20:42.573 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 02 15:20:42.573 INFO kablam! | Sep 02 15:20:42.573 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 02 15:20:42.573 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 02 15:20:42.573 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 02 15:20:42.574 INFO kablam! --> tests/lib.rs:18:1 Sep 02 15:20:42.574 INFO kablam! | Sep 02 15:20:42.574 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 02 15:20:42.574 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 02 15:20:42.574 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 15:20:42.574 INFO kablam! Sep 02 15:20:42.581 INFO kablam! error: aborting due to 3 previous errors Sep 02 15:20:42.581 INFO kablam! Sep 02 15:20:42.581 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 02 15:20:42.588 INFO kablam! error: Could not compile `entity_rust`. Sep 02 15:20:42.588 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 02 15:20:42.765 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 02 15:20:42.765 INFO kablam! --> tests/systems.rs:10:1 Sep 02 15:20:42.765 INFO kablam! | Sep 02 15:20:42.765 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Sep 02 15:20:42.765 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 02 15:20:42.765 INFO kablam! | Sep 02 15:20:42.765 INFO kablam! = note: expected type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.765 INFO kablam! found type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.765 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 02 15:20:42.765 INFO kablam! --> tests/systems.rs:10:1 Sep 02 15:20:42.765 INFO kablam! | Sep 02 15:20:42.765 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Sep 02 15:20:42.765 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 02 15:20:42.765 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 15:20:42.765 INFO kablam! Sep 02 15:20:42.769 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 02 15:20:42.769 INFO kablam! --> tests/systems.rs:11:1 Sep 02 15:20:42.769 INFO kablam! | Sep 02 15:20:42.769 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Sep 02 15:20:42.769 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 02 15:20:42.769 INFO kablam! | Sep 02 15:20:42.769 INFO kablam! = note: expected type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.769 INFO kablam! found type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.769 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 02 15:20:42.769 INFO kablam! --> tests/systems.rs:11:1 Sep 02 15:20:42.769 INFO kablam! | Sep 02 15:20:42.769 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Sep 02 15:20:42.769 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 02 15:20:42.769 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 15:20:42.769 INFO kablam! Sep 02 15:20:42.771 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 02 15:20:42.771 INFO kablam! --> tests/systems.rs:17:2 Sep 02 15:20:42.771 INFO kablam! | Sep 02 15:20:42.771 INFO kablam! 17 | component! { position, Sep 02 15:20:42.772 INFO kablam! | _____^ Sep 02 15:20:42.772 INFO kablam! 18 | | x: i64, Sep 02 15:20:42.772 INFO kablam! 19 | | y: i64 Sep 02 15:20:42.772 INFO kablam! 20 | | } Sep 02 15:20:42.772 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 02 15:20:42.772 INFO kablam! | Sep 02 15:20:42.772 INFO kablam! = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.772 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 02 15:20:42.772 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 02 15:20:42.772 INFO kablam! --> tests/systems.rs:17:2 Sep 02 15:20:42.772 INFO kablam! | Sep 02 15:20:42.772 INFO kablam! 17 | component! { position, Sep 02 15:20:42.772 INFO kablam! | _____^ Sep 02 15:20:42.772 INFO kablam! 18 | | x: i64, Sep 02 15:20:42.772 INFO kablam! 19 | | y: i64 Sep 02 15:20:42.772 INFO kablam! 20 | | } Sep 02 15:20:42.772 INFO kablam! | |_____^ Sep 02 15:20:42.772 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 15:20:42.772 INFO kablam! Sep 02 15:20:42.772 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 02 15:20:42.773 INFO kablam! --> tests/systems.rs:17:2 Sep 02 15:20:42.773 INFO kablam! | Sep 02 15:20:42.773 INFO kablam! 17 | component! { position, Sep 02 15:20:42.773 INFO kablam! | _____^ Sep 02 15:20:42.773 INFO kablam! 18 | | x: i64, Sep 02 15:20:42.773 INFO kablam! 19 | | y: i64 Sep 02 15:20:42.773 INFO kablam! 20 | | } Sep 02 15:20:42.773 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 02 15:20:42.773 INFO kablam! | Sep 02 15:20:42.773 INFO kablam! = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 02 15:20:42.773 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 02 15:20:42.773 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 02 15:20:42.773 INFO kablam! --> tests/systems.rs:17:2 Sep 02 15:20:42.773 INFO kablam! | Sep 02 15:20:42.773 INFO kablam! 17 | component! { position, Sep 02 15:20:42.773 INFO kablam! | _____^ Sep 02 15:20:42.773 INFO kablam! 18 | | x: i64, Sep 02 15:20:42.773 INFO kablam! 19 | | y: i64 Sep 02 15:20:42.773 INFO kablam! 20 | | } Sep 02 15:20:42.773 INFO kablam! | |_____^ Sep 02 15:20:42.773 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 15:20:42.774 INFO kablam! Sep 02 15:20:42.784 INFO kablam! error: aborting due to 4 previous errors Sep 02 15:20:42.784 INFO kablam! Sep 02 15:20:42.784 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 02 15:20:42.795 INFO kablam! error: Could not compile `entity_rust`. Sep 02 15:20:42.795 INFO kablam! Sep 02 15:20:42.795 INFO kablam! To learn more, run the command again with --verbose. Sep 02 15:20:42.796 INFO kablam! su: No module specific data is present Sep 02 15:20:43.146 INFO running `"docker" "rm" "-f" "940243b9d485205d890bbe10e6865238735884fa029f7fa3a3d6f65daff008e1"` Sep 02 15:20:43.237 INFO blam! 940243b9d485205d890bbe10e6865238735884fa029f7fa3a3d6f65daff008e1