Jul 12 10:18:43.856 INFO checking entity_rust-0.0.8 against master#ae5b629efd79de78e6ba7ef493c32857bd7f9cf9 for pr-52234 Jul 12 10:18:43.856 INFO running: cargo +ae5b629efd79de78e6ba7ef493c32857bd7f9cf9-alt check --frozen --all --all-targets Jul 12 10:18:43.856 INFO creating container for: cargo +ae5b629efd79de78e6ba7ef493c32857bd7f9cf9-alt check --frozen --all --all-targets Jul 12 10:18:43.856 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-2/pr-52234/master#ae5b629efd79de78e6ba7ef493c32857bd7f9cf9:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-52234/worker-2/master#ae5b629efd79de78e6ba7ef493c32857bd7f9cf9:/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 +ae5b629efd79de78e6ba7ef493c32857bd7f9cf9-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "crater"` Jul 12 10:18:44.114 INFO blam! 058bc730328c7a198e876ed607336176116e40c3aaece4855e78c29042a30400 Jul 12 10:18:44.116 INFO running `"docker" "start" "-a" "058bc730328c7a198e876ed607336176116e40c3aaece4855e78c29042a30400"` Jul 12 10:18:45.133 INFO kablam! Compiling poison v0.1.0 Jul 12 10:18:45.139 INFO kablam! Compiling uuid v0.6.5 Jul 12 10:18:46.769 INFO kablam! Checking shared-mutex v0.3.1 Jul 12 10:18:49.243 INFO kablam! Checking entity_rust v0.0.8 (file:///source) Jul 12 10:18:50.622 INFO kablam! warning: this feature has been stable since 1.13.0. Attribute no longer needed Jul 12 10:18:50.622 INFO kablam! --> src/lib.rs:1:12 Jul 12 10:18:50.622 INFO kablam! | Jul 12 10:18:50.622 INFO kablam! 1 | #![feature(type_macros)] Jul 12 10:18:50.622 INFO kablam! | ^^^^^^^^^^^ Jul 12 10:18:50.622 INFO kablam! | Jul 12 10:18:50.622 INFO kablam! = note: #[warn(stable_features)] on by default Jul 12 10:18:50.622 INFO kablam! Jul 12 10:18:50.885 INFO kablam! warning: this feature has been stable since 1.13.0. Attribute no longer needed Jul 12 10:18:50.885 INFO kablam! --> src/lib.rs:1:12 Jul 12 10:18:50.885 INFO kablam! | Jul 12 10:18:50.885 INFO kablam! 1 | #![feature(type_macros)] Jul 12 10:18:50.885 INFO kablam! | ^^^^^^^^^^^ Jul 12 10:18:50.885 INFO kablam! | Jul 12 10:18:50.885 INFO kablam! = note: #[warn(stable_features)] on by default Jul 12 10:18:50.885 INFO kablam! Jul 12 10:18:51.008 INFO kablam! warning: this feature has been stable since 1.13.0. Attribute no longer needed Jul 12 10:18:51.008 INFO kablam! --> src/lib.rs:1:12 Jul 12 10:18:51.008 INFO kablam! | Jul 12 10:18:51.008 INFO kablam! 1 | #![feature(type_macros)] Jul 12 10:18:51.008 INFO kablam! | ^^^^^^^^^^^ Jul 12 10:18:51.008 INFO kablam! | Jul 12 10:18:51.008 INFO kablam! = note: #[warn(stable_features)] on by default Jul 12 10:18:51.008 INFO kablam! Jul 12 10:18:58.310 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Jul 12 10:18:58.310 INFO kablam! --> tests/systems.rs:10:1 Jul 12 10:18:58.310 INFO kablam! | Jul 12 10:18:58.310 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Jul 12 10:18:58.310 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Jul 12 10:18:58.320 INFO kablam! warning: variable does not need to be mutable Jul 12 10:18:58.320 INFO kablam! --> tests/static_any_map.rs:9:1 Jul 12 10:18:58.320 INFO kablam! | Jul 12 10:18:58.320 INFO kablam! 9 | static_any_vec_map! { my_map, String } Jul 12 10:18:58.320 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut` Jul 12 10:18:58.329 INFO kablam! | Jul 12 10:18:58.329 INFO kablam! = note: #[warn(unused_mut)] on by default Jul 12 10:18:58.329 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) Jul 12 10:18:58.330 INFO kablam! Jul 12 10:18:58.330 INFO kablam! warning: variable does not need to be mutable Jul 12 10:18:58.330 INFO kablam! --> tests/static_any_map.rs:9:1 Jul 12 10:18:58.330 INFO kablam! | Jul 12 10:18:58.330 INFO kablam! 9 | static_any_vec_map! { my_map, String } Jul 12 10:18:58.330 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut` Jul 12 10:18:58.330 INFO kablam! | Jul 12 10:18:58.330 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) Jul 12 10:18:58.330 INFO kablam! Jul 12 10:18:58.330 INFO kablam! | Jul 12 10:18:58.330 INFO kablam! = note: expected type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.330 INFO kablam! found type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.331 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Jul 12 10:18:58.331 INFO kablam! --> tests/systems.rs:10:1 Jul 12 10:18:58.331 INFO kablam! | Jul 12 10:18:58.331 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Jul 12 10:18:58.331 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 12 10:18:58.331 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) Jul 12 10:18:58.331 INFO kablam! Jul 12 10:18:58.331 INFO kablam! warning: variable does not need to be mutable Jul 12 10:18:58.331 INFO kablam! --> tests/static_any_map.rs:9:1 Jul 12 10:18:58.331 INFO kablam! | Jul 12 10:18:58.331 INFO kablam! 9 | static_any_vec_map! { my_map, String } Jul 12 10:18:58.331 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut` Jul 12 10:18:58.331 INFO kablam! | Jul 12 10:18:58.331 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) Jul 12 10:18:58.331 INFO kablam! Jul 12 10:18:58.350 INFO kablam! warning: variable does not need to be mutable Jul 12 10:18:58.350 INFO kablam! --> tests/static_any_map.rs:9:1 Jul 12 10:18:58.351 INFO kablam! | Jul 12 10:18:58.351 INFO kablam! 9 | static_any_vec_map! { my_map, String } Jul 12 10:18:58.351 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut` Jul 12 10:18:58.351 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Jul 12 10:18:58.351 INFO kablam! --> tests/systems.rs:11:1 Jul 12 10:18:58.351 INFO kablam! | Jul 12 10:18:58.351 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Jul 12 10:18:58.351 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Jul 12 10:18:58.352 INFO kablam! | Jul 12 10:18:58.352 INFO kablam! = note: expected type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.352 INFO kablam! found type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.352 INFO kablam! | Jul 12 10:18:58.352 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Jul 12 10:18:58.352 INFO kablam! --> tests/systems.rs:11:1 Jul 12 10:18:58.352 INFO kablam! | Jul 12 10:18:58.352 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Jul 12 10:18:58.352 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 12 10:18:58.352 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) Jul 12 10:18:58.352 INFO kablam! Jul 12 10:18:58.352 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) Jul 12 10:18:58.352 INFO kablam! Jul 12 10:18:58.353 INFO kablam! warning: variable does not need to be mutable Jul 12 10:18:58.353 INFO kablam! --> tests/static_any_map.rs:9:1 Jul 12 10:18:58.353 INFO kablam! | Jul 12 10:18:58.353 INFO kablam! 9 | static_any_vec_map! { my_map, String } Jul 12 10:18:58.353 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut` Jul 12 10:18:58.353 INFO kablam! | Jul 12 10:18:58.353 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) Jul 12 10:18:58.353 INFO kablam! Jul 12 10:18:58.353 INFO kablam! warning: variable does not need to be mutable Jul 12 10:18:58.353 INFO kablam! --> tests/static_any_map.rs:9:1 Jul 12 10:18:58.353 INFO kablam! | Jul 12 10:18:58.353 INFO kablam! 9 | static_any_vec_map! { my_map, String } Jul 12 10:18:58.353 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut` Jul 12 10:18:58.353 INFO kablam! | Jul 12 10:18:58.353 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) Jul 12 10:18:58.353 INFO kablam! Jul 12 10:18:58.354 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Jul 12 10:18:58.354 INFO kablam! --> tests/systems.rs:17:2 Jul 12 10:18:58.354 INFO kablam! | Jul 12 10:18:58.354 INFO kablam! 17 | component! { position, Jul 12 10:18:58.354 INFO kablam! | _____^ Jul 12 10:18:58.354 INFO kablam! 18 | | x: i64, Jul 12 10:18:58.355 INFO kablam! 19 | | y: i64 Jul 12 10:18:58.355 INFO kablam! 20 | | } Jul 12 10:18:58.355 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Jul 12 10:18:58.355 INFO kablam! | Jul 12 10:18:58.355 INFO kablam! = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.355 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.375 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Jul 12 10:18:58.375 INFO kablam! --> tests/systems.rs:17:2 Jul 12 10:18:58.375 INFO kablam! | Jul 12 10:18:58.375 INFO kablam! 17 | component! { position, Jul 12 10:18:58.375 INFO kablam! | _____^ Jul 12 10:18:58.375 INFO kablam! 18 | | x: i64, Jul 12 10:18:58.375 INFO kablam! 19 | | y: i64 Jul 12 10:18:58.375 INFO kablam! 20 | | } Jul 12 10:18:58.375 INFO kablam! | |_____^ Jul 12 10:18:58.375 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) Jul 12 10:18:58.375 INFO kablam! Jul 12 10:18:58.376 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Jul 12 10:18:58.376 INFO kablam! --> tests/systems.rs:17:2 Jul 12 10:18:58.376 INFO kablam! | Jul 12 10:18:58.376 INFO kablam! 17 | component! { position, Jul 12 10:18:58.376 INFO kablam! | _____^ Jul 12 10:18:58.376 INFO kablam! 18 | | x: i64, Jul 12 10:18:58.376 INFO kablam! 19 | | y: i64 Jul 12 10:18:58.376 INFO kablam! 20 | | } Jul 12 10:18:58.376 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Jul 12 10:18:58.376 INFO kablam! | Jul 12 10:18:58.376 INFO kablam! = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Jul 12 10:18:58.376 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Jul 12 10:18:58.376 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Jul 12 10:18:58.376 INFO kablam! --> tests/systems.rs:17:2 Jul 12 10:18:58.376 INFO kablam! | Jul 12 10:18:58.376 INFO kablam! 17 | component! { position, Jul 12 10:18:58.376 INFO kablam! | _____^ Jul 12 10:18:58.376 INFO kablam! 18 | | x: i64, Jul 12 10:18:58.376 INFO kablam! 19 | | y: i64 Jul 12 10:18:58.377 INFO kablam! 20 | | } Jul 12 10:18:58.377 INFO kablam! | |_____^ Jul 12 10:18:58.377 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) Jul 12 10:18:58.377 INFO kablam! Jul 12 10:18:58.421 INFO kablam! error: aborting due to 4 previous errors Jul 12 10:18:58.421 INFO kablam! Jul 12 10:18:58.421 INFO kablam! For more information about this error, try `rustc --explain E0053`. Jul 12 10:18:58.495 INFO kablam! error: Could not compile `entity_rust`. Jul 12 10:18:58.495 INFO kablam! warning: build failed, waiting for other jobs to finish... Jul 12 10:18:58.593 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Jul 12 10:18:58.593 INFO kablam! --> tests/lib.rs:16:1 Jul 12 10:18:58.593 INFO kablam! | Jul 12 10:18:58.593 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Jul 12 10:18:58.593 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Jul 12 10:18:58.602 INFO kablam! | Jul 12 10:18:58.603 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.603 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.603 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Jul 12 10:18:58.603 INFO kablam! --> tests/lib.rs:16:1 Jul 12 10:18:58.603 INFO kablam! | Jul 12 10:18:58.603 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Jul 12 10:18:58.604 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 12 10:18:58.604 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) Jul 12 10:18:58.604 INFO kablam! Jul 12 10:18:58.611 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Jul 12 10:18:58.611 INFO kablam! --> tests/lib.rs:18:1 Jul 12 10:18:58.611 INFO kablam! | Jul 12 10:18:58.611 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Jul 12 10:18:58.611 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Jul 12 10:18:58.612 INFO kablam! | Jul 12 10:18:58.612 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.612 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.612 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Jul 12 10:18:58.612 INFO kablam! --> tests/lib.rs:18:1 Jul 12 10:18:58.612 INFO kablam! | Jul 12 10:18:58.613 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Jul 12 10:18:58.613 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 12 10:18:58.613 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) Jul 12 10:18:58.613 INFO kablam! Jul 12 10:18:58.614 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Jul 12 10:18:58.614 INFO kablam! --> tests/lib.rs:18:1 Jul 12 10:18:58.614 INFO kablam! | Jul 12 10:18:58.614 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Jul 12 10:18:58.614 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Jul 12 10:18:58.615 INFO kablam! | Jul 12 10:18:58.615 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Jul 12 10:18:58.615 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Jul 12 10:18:58.615 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Jul 12 10:18:58.615 INFO kablam! --> tests/lib.rs:18:1 Jul 12 10:18:58.615 INFO kablam! | Jul 12 10:18:58.616 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Jul 12 10:18:58.616 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 12 10:18:58.616 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) Jul 12 10:18:58.616 INFO kablam! Jul 12 10:18:58.627 INFO kablam! error: aborting due to 3 previous errors Jul 12 10:18:58.627 INFO kablam! Jul 12 10:18:58.628 INFO kablam! For more information about this error, try `rustc --explain E0053`. Jul 12 10:18:58.639 INFO kablam! error: Could not compile `entity_rust`. Jul 12 10:18:58.640 INFO kablam! warning: build failed, waiting for other jobs to finish... Jul 12 10:18:58.834 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Jul 12 10:18:58.834 INFO kablam! --> tests/components.rs:7:1 Jul 12 10:18:58.834 INFO kablam! | Jul 12 10:18:58.834 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Jul 12 10:18:58.834 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Jul 12 10:18:58.850 INFO kablam! | Jul 12 10:18:58.851 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.851 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.851 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Jul 12 10:18:58.851 INFO kablam! --> tests/components.rs:7:1 Jul 12 10:18:58.851 INFO kablam! | Jul 12 10:18:58.851 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Jul 12 10:18:58.852 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 12 10:18:58.852 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) Jul 12 10:18:58.852 INFO kablam! Jul 12 10:18:58.853 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Jul 12 10:18:58.853 INFO kablam! --> tests/components.rs:7:1 Jul 12 10:18:58.853 INFO kablam! | Jul 12 10:18:58.853 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Jul 12 10:18:58.853 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Jul 12 10:18:58.854 INFO kablam! | Jul 12 10:18:58.854 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Jul 12 10:18:58.854 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Jul 12 10:18:58.854 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Jul 12 10:18:58.854 INFO kablam! --> tests/components.rs:7:1 Jul 12 10:18:58.855 INFO kablam! | Jul 12 10:18:58.855 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Jul 12 10:18:58.855 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 12 10:18:58.855 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) Jul 12 10:18:58.855 INFO kablam! Jul 12 10:18:58.896 INFO kablam! error: aborting due to 2 previous errors Jul 12 10:18:58.896 INFO kablam! Jul 12 10:18:58.896 INFO kablam! For more information about this error, try `rustc --explain E0053`. Jul 12 10:18:58.917 INFO kablam! error: Could not compile `entity_rust`. Jul 12 10:18:58.917 INFO kablam! warning: build failed, waiting for other jobs to finish... Jul 12 10:18:58.988 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Jul 12 10:18:58.988 INFO kablam! --> tests/events.rs:8:1 Jul 12 10:18:58.988 INFO kablam! | Jul 12 10:18:58.988 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Jul 12 10:18:58.988 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Jul 12 10:18:58.988 INFO kablam! | Jul 12 10:18:58.988 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.988 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Jul 12 10:18:58.989 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Jul 12 10:18:58.989 INFO kablam! --> tests/events.rs:8:1 Jul 12 10:18:58.989 INFO kablam! | Jul 12 10:18:58.989 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Jul 12 10:18:58.990 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 12 10:18:58.990 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) Jul 12 10:18:58.990 INFO kablam! Jul 12 10:18:58.998 INFO kablam! error: aborting due to previous error Jul 12 10:18:58.998 INFO kablam! Jul 12 10:18:58.998 INFO kablam! For more information about this error, try `rustc --explain E0053`. Jul 12 10:18:59.021 INFO kablam! error: Could not compile `entity_rust`. Jul 12 10:18:59.021 INFO kablam! Jul 12 10:18:59.021 INFO kablam! To learn more, run the command again with --verbose. Jul 12 10:18:59.031 INFO kablam! su: No module specific data is present Jul 12 10:18:59.622 INFO running `"docker" "rm" "-f" "058bc730328c7a198e876ed607336176116e40c3aaece4855e78c29042a30400"` Jul 12 10:18:59.796 INFO blam! 058bc730328c7a198e876ed607336176116e40c3aaece4855e78c29042a30400