Sep 04 18:40:07.528 INFO checking entity_rust-0.0.8 against master#28bcffead74d5e17c6cb1f7de432e37f93a6b50c for pr-53893 Sep 04 18:40:07.528 INFO running: cargo +28bcffead74d5e17c6cb1f7de432e37f93a6b50c-alt check --frozen --all --all-targets Sep 04 18:40:07.528 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-1/pr-53893/master#28bcffead74d5e17c6cb1f7de432e37f93a6b50c:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53893/worker-1/master#28bcffead74d5e17c6cb1f7de432e37f93a6b50c:/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 +28bcffead74d5e17c6cb1f7de432e37f93a6b50c-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Sep 04 18:40:07.757 INFO blam! ecc78edca1497878c17e31a5895515fbdcea08864c46489366dd70b2fedfb650 Sep 04 18:40:07.759 INFO running `"docker" "start" "-a" "ecc78edca1497878c17e31a5895515fbdcea08864c46489366dd70b2fedfb650"` Sep 04 18:40:08.469 INFO kablam! Compiling poison v0.1.0 Sep 04 18:40:08.472 INFO kablam! Checking uuid v0.6.5 Sep 04 18:40:09.407 INFO kablam! Compiling shared-mutex v0.3.1 Sep 04 18:40:11.016 INFO kablam! Checking entity_rust v0.0.8 (file:///source) Sep 04 18:40:12.302 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Sep 04 18:40:12.302 INFO kablam! --> src/lib.rs:1:12 Sep 04 18:40:12.302 INFO kablam! | Sep 04 18:40:12.302 INFO kablam! 1 | #![feature(type_macros)] Sep 04 18:40:12.302 INFO kablam! | ^^^^^^^^^^^ Sep 04 18:40:12.302 INFO kablam! | Sep 04 18:40:12.302 INFO kablam! = note: #[warn(stable_features)] on by default Sep 04 18:40:12.302 INFO kablam! Sep 04 18:40:12.512 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Sep 04 18:40:12.512 INFO kablam! --> src/lib.rs:1:12 Sep 04 18:40:12.512 INFO kablam! | Sep 04 18:40:12.512 INFO kablam! 1 | #![feature(type_macros)] Sep 04 18:40:12.512 INFO kablam! | ^^^^^^^^^^^ Sep 04 18:40:12.512 INFO kablam! | Sep 04 18:40:12.512 INFO kablam! = note: #[warn(stable_features)] on by default Sep 04 18:40:12.512 INFO kablam! Sep 04 18:40:12.513 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Sep 04 18:40:12.513 INFO kablam! --> src/lib.rs:1:12 Sep 04 18:40:12.513 INFO kablam! | Sep 04 18:40:12.513 INFO kablam! 1 | #![feature(type_macros)] Sep 04 18:40:12.513 INFO kablam! | ^^^^^^^^^^^ Sep 04 18:40:12.513 INFO kablam! | Sep 04 18:40:12.513 INFO kablam! = note: #[warn(stable_features)] on by default Sep 04 18:40:12.513 INFO kablam! Sep 04 18:40:16.298 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 04 18:40:16.299 INFO kablam! --> tests/components.rs:7:1 Sep 04 18:40:16.299 INFO kablam! | Sep 04 18:40:16.299 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 04 18:40:16.299 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 18:40:16.299 INFO kablam! | Sep 04 18:40:16.299 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:16.299 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:16.299 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 18:40:16.299 INFO kablam! --> tests/components.rs:7:1 Sep 04 18:40:16.299 INFO kablam! | Sep 04 18:40:16.299 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 04 18:40:16.299 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 18:40:16.299 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 04 18:40:16.299 INFO kablam! Sep 04 18:40:16.300 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 04 18:40:16.300 INFO kablam! --> tests/components.rs:7:1 Sep 04 18:40:16.300 INFO kablam! | Sep 04 18:40:16.300 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 04 18:40:16.300 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 04 18:40:16.300 INFO kablam! | Sep 04 18:40:16.300 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 04 18:40:16.300 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 04 18:40:16.300 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 18:40:16.300 INFO kablam! --> tests/components.rs:7:1 Sep 04 18:40:16.300 INFO kablam! | Sep 04 18:40:16.300 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 04 18:40:16.300 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 18:40:16.300 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 04 18:40:16.300 INFO kablam! Sep 04 18:40:16.360 INFO kablam! error: aborting due to 2 previous errors Sep 04 18:40:16.360 INFO kablam! Sep 04 18:40:16.360 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 04 18:40:16.369 INFO kablam! error: Could not compile `entity_rust`. Sep 04 18:40:16.369 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 04 18:40:16.698 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 04 18:40:16.698 INFO kablam! --> tests/events.rs:8:1 Sep 04 18:40:16.698 INFO kablam! | Sep 04 18:40:16.698 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Sep 04 18:40:16.698 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 18:40:16.698 INFO kablam! | Sep 04 18:40:16.698 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:16.698 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:16.698 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 18:40:16.698 INFO kablam! --> tests/events.rs:8:1 Sep 04 18:40:16.698 INFO kablam! | Sep 04 18:40:16.698 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Sep 04 18:40:16.698 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 18:40:16.698 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 04 18:40:16.698 INFO kablam! Sep 04 18:40:16.708 INFO kablam! error: aborting due to previous error Sep 04 18:40:16.709 INFO kablam! Sep 04 18:40:16.709 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 04 18:40:16.719 INFO kablam! error: Could not compile `entity_rust`. Sep 04 18:40:16.719 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 04 18:40:17.017 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 04 18:40:17.017 INFO kablam! --> tests/lib.rs:16:1 Sep 04 18:40:17.017 INFO kablam! | Sep 04 18:40:17.017 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Sep 04 18:40:17.017 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 18:40:17.017 INFO kablam! | Sep 04 18:40:17.017 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:17.017 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:17.018 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 18:40:17.018 INFO kablam! --> tests/lib.rs:16:1 Sep 04 18:40:17.018 INFO kablam! | Sep 04 18:40:17.018 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Sep 04 18:40:17.018 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 18:40:17.018 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 04 18:40:17.018 INFO kablam! Sep 04 18:40:17.023 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 04 18:40:17.023 INFO kablam! --> tests/lib.rs:18:1 Sep 04 18:40:17.023 INFO kablam! | Sep 04 18:40:17.023 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 04 18:40:17.023 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 18:40:17.023 INFO kablam! | Sep 04 18:40:17.023 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:17.023 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:17.024 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 18:40:17.024 INFO kablam! --> tests/lib.rs:18:1 Sep 04 18:40:17.024 INFO kablam! | Sep 04 18:40:17.024 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 04 18:40:17.024 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 18:40:17.024 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 04 18:40:17.024 INFO kablam! Sep 04 18:40:17.024 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 04 18:40:17.024 INFO kablam! --> tests/lib.rs:18:1 Sep 04 18:40:17.024 INFO kablam! | Sep 04 18:40:17.024 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 04 18:40:17.024 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 04 18:40:17.024 INFO kablam! | Sep 04 18:40:17.024 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 04 18:40:17.024 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 04 18:40:17.024 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 18:40:17.024 INFO kablam! --> tests/lib.rs:18:1 Sep 04 18:40:17.024 INFO kablam! | Sep 04 18:40:17.025 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 04 18:40:17.025 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 18:40:17.025 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 04 18:40:17.025 INFO kablam! Sep 04 18:40:17.035 INFO kablam! error: aborting due to 3 previous errors Sep 04 18:40:17.035 INFO kablam! Sep 04 18:40:17.035 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 04 18:40:17.044 INFO kablam! error: Could not compile `entity_rust`. Sep 04 18:40:17.044 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 04 18:40:17.172 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 04 18:40:17.172 INFO kablam! --> tests/systems.rs:10:1 Sep 04 18:40:17.172 INFO kablam! | Sep 04 18:40:17.172 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Sep 04 18:40:17.173 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 18:40:17.173 INFO kablam! | Sep 04 18:40:17.173 INFO kablam! = note: expected type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:17.173 INFO kablam! found type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:17.173 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 18:40:17.173 INFO kablam! --> tests/systems.rs:10:1 Sep 04 18:40:17.173 INFO kablam! | Sep 04 18:40:17.173 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Sep 04 18:40:17.173 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 18:40:17.173 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 04 18:40:17.173 INFO kablam! Sep 04 18:40:17.177 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 04 18:40:17.177 INFO kablam! --> tests/systems.rs:11:1 Sep 04 18:40:17.178 INFO kablam! | Sep 04 18:40:17.178 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Sep 04 18:40:17.178 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 18:40:17.178 INFO kablam! | Sep 04 18:40:17.178 INFO kablam! = note: expected type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:17.178 INFO kablam! found type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:17.178 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 18:40:17.178 INFO kablam! --> tests/systems.rs:11:1 Sep 04 18:40:17.178 INFO kablam! | Sep 04 18:40:17.178 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Sep 04 18:40:17.178 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 18:40:17.178 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 04 18:40:17.178 INFO kablam! Sep 04 18:40:17.180 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 04 18:40:17.180 INFO kablam! --> tests/systems.rs:17:2 Sep 04 18:40:17.180 INFO kablam! | Sep 04 18:40:17.181 INFO kablam! 17 | component! { position, Sep 04 18:40:17.181 INFO kablam! | _____^ Sep 04 18:40:17.181 INFO kablam! 18 | | x: i64, Sep 04 18:40:17.181 INFO kablam! 19 | | y: i64 Sep 04 18:40:17.181 INFO kablam! 20 | | } Sep 04 18:40:17.181 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 18:40:17.181 INFO kablam! | Sep 04 18:40:17.181 INFO kablam! = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:17.181 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 18:40:17.181 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 18:40:17.181 INFO kablam! --> tests/systems.rs:17:2 Sep 04 18:40:17.181 INFO kablam! | Sep 04 18:40:17.181 INFO kablam! 17 | component! { position, Sep 04 18:40:17.181 INFO kablam! | _____^ Sep 04 18:40:17.181 INFO kablam! 18 | | x: i64, Sep 04 18:40:17.181 INFO kablam! 19 | | y: i64 Sep 04 18:40:17.181 INFO kablam! 20 | | } Sep 04 18:40:17.181 INFO kablam! | |_____^ Sep 04 18:40:17.181 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 04 18:40:17.181 INFO kablam! Sep 04 18:40:17.181 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 04 18:40:17.181 INFO kablam! --> tests/systems.rs:17:2 Sep 04 18:40:17.181 INFO kablam! | Sep 04 18:40:17.181 INFO kablam! 17 | component! { position, Sep 04 18:40:17.181 INFO kablam! | _____^ Sep 04 18:40:17.181 INFO kablam! 18 | | x: i64, Sep 04 18:40:17.181 INFO kablam! 19 | | y: i64 Sep 04 18:40:17.182 INFO kablam! 20 | | } Sep 04 18:40:17.182 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 04 18:40:17.182 INFO kablam! | Sep 04 18:40:17.182 INFO kablam! = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 04 18:40:17.182 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 04 18:40:17.182 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 18:40:17.182 INFO kablam! --> tests/systems.rs:17:2 Sep 04 18:40:17.182 INFO kablam! | Sep 04 18:40:17.182 INFO kablam! 17 | component! { position, Sep 04 18:40:17.182 INFO kablam! | _____^ Sep 04 18:40:17.182 INFO kablam! 18 | | x: i64, Sep 04 18:40:17.182 INFO kablam! 19 | | y: i64 Sep 04 18:40:17.182 INFO kablam! 20 | | } Sep 04 18:40:17.182 INFO kablam! | |_____^ Sep 04 18:40:17.182 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 04 18:40:17.182 INFO kablam! Sep 04 18:40:17.192 INFO kablam! error: aborting due to 4 previous errors Sep 04 18:40:17.192 INFO kablam! Sep 04 18:40:17.192 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 04 18:40:17.202 INFO kablam! error: Could not compile `entity_rust`. Sep 04 18:40:17.202 INFO kablam! Sep 04 18:40:17.203 INFO kablam! To learn more, run the command again with --verbose. Sep 04 18:40:17.204 INFO kablam! su: No module specific data is present Sep 04 18:40:17.696 INFO running `"docker" "rm" "-f" "ecc78edca1497878c17e31a5895515fbdcea08864c46489366dd70b2fedfb650"` Sep 04 18:40:17.789 INFO blam! ecc78edca1497878c17e31a5895515fbdcea08864c46489366dd70b2fedfb650