Jul 12 10:18:43.665 INFO checking entity_rust-0.0.8 against try#d39a6f7eddafd45dcc60e99001b8cd08c2bd3255 for pr-52234
Jul 12 10:18:43.665 INFO running: cargo +d39a6f7eddafd45dcc60e99001b8cd08c2bd3255-alt check --frozen --all --all-targets
Jul 12 10:18:43.665 INFO creating container for: cargo +d39a6f7eddafd45dcc60e99001b8cd08c2bd3255-alt check --frozen --all --all-targets
Jul 12 10:18:43.665 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-3/pr-52234/try#d39a6f7eddafd45dcc60e99001b8cd08c2bd3255:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-52234/worker-3/try#d39a6f7eddafd45dcc60e99001b8cd08c2bd3255:/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 +d39a6f7eddafd45dcc60e99001b8cd08c2bd3255-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "crater"`
Jul 12 10:18:43.886 INFO blam! 7cdc86cda88d2bd0cd371a4707758d9443f509e9fc8da0187a947f589205c057
Jul 12 10:18:43.889 INFO running `"docker" "start" "-a" "7cdc86cda88d2bd0cd371a4707758d9443f509e9fc8da0187a947f589205c057"`
Jul 12 10:18:44.968 INFO kablam!    Compiling poison v0.1.0
Jul 12 10:18:44.971 INFO kablam!     Checking uuid v0.6.5
Jul 12 10:18:46.586 INFO kablam!     Checking shared-mutex v0.3.1
Jul 12 10:18:49.047 INFO kablam!     Checking entity_rust v0.0.8 (file:///source)
Jul 12 10:18:50.412 INFO kablam! warning: this feature has been stable since 1.13.0. Attribute no longer needed
Jul 12 10:18:50.412 INFO kablam!  --> src/lib.rs:1:12
Jul 12 10:18:50.412 INFO kablam!   |
Jul 12 10:18:50.412 INFO kablam! 1 | #![feature(type_macros)]
Jul 12 10:18:50.412 INFO kablam!   |            ^^^^^^^^^^^
Jul 12 10:18:50.412 INFO kablam!   |
Jul 12 10:18:50.413 INFO kablam!   = note: #[warn(stable_features)] on by default
Jul 12 10:18:50.413 INFO kablam! 
Jul 12 10:18:50.529 INFO kablam! warning: this feature has been stable since 1.13.0. Attribute no longer needed
Jul 12 10:18:50.529 INFO kablam!  --> src/lib.rs:1:12
Jul 12 10:18:50.529 INFO kablam!   |
Jul 12 10:18:50.529 INFO kablam! 1 | #![feature(type_macros)]
Jul 12 10:18:50.529 INFO kablam!   |            ^^^^^^^^^^^
Jul 12 10:18:50.529 INFO kablam!   |
Jul 12 10:18:50.529 INFO kablam!   = note: #[warn(stable_features)] on by default
Jul 12 10:18:50.529 INFO kablam! 
Jul 12 10:18:50.652 INFO kablam! warning: this feature has been stable since 1.13.0. Attribute no longer needed
Jul 12 10:18:50.652 INFO kablam!  --> src/lib.rs:1:12
Jul 12 10:18:50.653 INFO kablam!   |
Jul 12 10:18:50.653 INFO kablam! 1 | #![feature(type_macros)]
Jul 12 10:18:50.653 INFO kablam!   |            ^^^^^^^^^^^
Jul 12 10:18:50.653 INFO kablam!   |
Jul 12 10:18:50.653 INFO kablam!   = note: #[warn(stable_features)] on by default
Jul 12 10:18:50.653 INFO kablam! 
Jul 12 10:18:58.181 INFO kablam! warning: variable does not need to be mutable
Jul 12 10:18:58.181 INFO kablam!  --> tests/static_any_map.rs:9:1
Jul 12 10:18:58.181 INFO kablam!   |
Jul 12 10:18:58.181 INFO kablam! 9 | static_any_vec_map! { my_map, String }
Jul 12 10:18:58.181 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut`
Jul 12 10:18:58.181 INFO kablam!   |
Jul 12 10:18:58.181 INFO kablam!   = note: #[warn(unused_mut)] on by default
Jul 12 10:18:58.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)
Jul 12 10:18:58.181 INFO kablam! 
Jul 12 10:18:58.182 INFO kablam! warning: variable does not need to be mutable
Jul 12 10:18:58.182 INFO kablam!  --> tests/static_any_map.rs:9:1
Jul 12 10:18:58.182 INFO kablam!   |
Jul 12 10:18:58.182 INFO kablam! 9 | static_any_vec_map! { my_map, String }
Jul 12 10:18:58.183 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut`
Jul 12 10:18:58.183 INFO kablam!   |
Jul 12 10:18:58.183 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.183 INFO kablam! 
Jul 12 10:18:58.183 INFO kablam! warning: variable does not need to be mutable
Jul 12 10:18:58.183 INFO kablam!  --> tests/static_any_map.rs:9:1
Jul 12 10:18:58.183 INFO kablam!   |
Jul 12 10:18:58.183 INFO kablam! 9 | static_any_vec_map! { my_map, String }
Jul 12 10:18:58.183 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut`
Jul 12 10:18:58.183 INFO kablam!   |
Jul 12 10:18:58.183 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.183 INFO kablam! 
Jul 12 10:18:58.187 INFO kablam! warning: variable does not need to be mutable
Jul 12 10:18:58.187 INFO kablam!  --> tests/static_any_map.rs:9:1
Jul 12 10:18:58.187 INFO kablam!   |
Jul 12 10:18:58.187 INFO kablam! 9 | static_any_vec_map! { my_map, String }
Jul 12 10:18:58.187 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut`
Jul 12 10:18:58.188 INFO kablam!   |
Jul 12 10:18:58.188 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.188 INFO kablam! 
Jul 12 10:18:58.188 INFO kablam! warning: variable does not need to be mutable
Jul 12 10:18:58.189 INFO kablam!  --> tests/static_any_map.rs:9:1
Jul 12 10:18:58.189 INFO kablam!   |
Jul 12 10:18:58.189 INFO kablam! 9 | static_any_vec_map! { my_map, String }
Jul 12 10:18:58.189 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut`
Jul 12 10:18:58.189 INFO kablam!   |
Jul 12 10:18:58.189 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.189 INFO kablam! 
Jul 12 10:18:58.189 INFO kablam! warning: variable does not need to be mutable
Jul 12 10:18:58.189 INFO kablam!  --> tests/static_any_map.rs:9:1
Jul 12 10:18:58.189 INFO kablam!   |
Jul 12 10:18:58.189 INFO kablam! 9 | static_any_vec_map! { my_map, String }
Jul 12 10:18:58.189 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove this `mut`
Jul 12 10:18:58.189 INFO kablam!   |
Jul 12 10:18:58.189 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.189 INFO kablam! 
Jul 12 10:18:58.395 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait
Jul 12 10:18:58.396 INFO kablam!  --> tests/components.rs:7:1
Jul 12 10:18:58.396 INFO kablam!   |
Jul 12 10:18:58.396 INFO kablam! 7 | component! { test_component, a: i64, b: i64 }
Jul 12 10:18:58.396 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Jul 12 10:18:58.396 INFO kablam!   |
Jul 12 10:18:58.396 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.396 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.396 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Jul 12 10:18:58.396 INFO kablam!  --> tests/components.rs:7:1
Jul 12 10:18:58.396 INFO kablam!   |
Jul 12 10:18:58.396 INFO kablam! 7 | component! { test_component, a: i64, b: i64 }
Jul 12 10:18:58.396 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 12 10:18:58.397 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.397 INFO kablam! 
Jul 12 10:18:58.397 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait
Jul 12 10:18:58.397 INFO kablam!  --> tests/components.rs:7:1
Jul 12 10:18:58.397 INFO kablam!   |
Jul 12 10:18:58.397 INFO kablam! 7 | component! { test_component, a: i64, b: i64 }
Jul 12 10:18:58.397 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard`
Jul 12 10:18:58.398 INFO kablam!   |
Jul 12 10:18:58.398 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.398 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.398 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Jul 12 10:18:58.399 INFO kablam!  --> tests/components.rs:7:1
Jul 12 10:18:58.399 INFO kablam!   |
Jul 12 10:18:58.399 INFO kablam! 7 | component! { test_component, a: i64, b: i64 }
Jul 12 10:18:58.399 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 12 10:18:58.399 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.399 INFO kablam! 
Jul 12 10:18:58.425 INFO kablam! error: aborting due to 2 previous errors
Jul 12 10:18:58.425 INFO kablam! 
Jul 12 10:18:58.426 INFO kablam! For more information about this error, try `rustc --explain E0053`.
Jul 12 10:18:58.436 INFO kablam! error: Could not compile `entity_rust`.
Jul 12 10:18:58.437 INFO kablam! warning: build failed, waiting for other jobs to finish...
Jul 12 10:18:58.694 INFO kablam! error[E0053]: method `run` has an incompatible type for trait
Jul 12 10:18:58.694 INFO kablam!   --> tests/systems.rs:10:1
Jul 12 10:18:58.694 INFO kablam!    |
Jul 12 10:18:58.694 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 }
Jul 12 10:18:58.694 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Jul 12 10:18:58.694 INFO kablam!    |
Jul 12 10:18:58.695 INFO kablam!    = note: expected type `fn(&my_event::HandlerInstance, std::vec::Vec<shared_mutex::MappedSharedMutexReadGuard<'_, (dyn std::any::Any + 'static)>>, std::vec::Vec<shared_mutex::MappedSharedMutexWriteGuard<'_, (dyn std::any::Any + 'static)>>)` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Jul 12 10:18:58.695 INFO kablam!               found type `fn(&my_event::HandlerInstance, std::vec::Vec<shared_mutex::MappedSharedMutexReadGuard<'_, (dyn std::any::Any + 'static)>>, std::vec::Vec<shared_mutex::MappedSharedMutexWriteGuard<'_, (dyn std::any::Any + 'static)>>)` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Jul 12 10:18:58.695 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Jul 12 10:18:58.695 INFO kablam!   --> tests/systems.rs:10:1
Jul 12 10:18:58.695 INFO kablam!    |
Jul 12 10:18:58.695 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 }
Jul 12 10:18:58.695 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 12 10:18:58.695 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.695 INFO kablam! 
Jul 12 10:18:58.719 INFO kablam! error[E0053]: method `run` has an incompatible type for trait
Jul 12 10:18:58.719 INFO kablam!   --> tests/systems.rs:11:1
Jul 12 10:18:58.719 INFO kablam!    |
Jul 12 10:18:58.719 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 }
Jul 12 10:18:58.719 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Jul 12 10:18:58.719 INFO kablam!    |
Jul 12 10:18:58.719 INFO kablam!    = note: expected type `fn(&my_event_2::HandlerInstance, std::vec::Vec<shared_mutex::MappedSharedMutexReadGuard<'_, (dyn std::any::Any + 'static)>>, std::vec::Vec<shared_mutex::MappedSharedMutexWriteGuard<'_, (dyn std::any::Any + 'static)>>)` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Jul 12 10:18:58.719 INFO kablam!               found type `fn(&my_event_2::HandlerInstance, std::vec::Vec<shared_mutex::MappedSharedMutexReadGuard<'_, (dyn std::any::Any + 'static)>>, std::vec::Vec<shared_mutex::MappedSharedMutexWriteGuard<'_, (dyn std::any::Any + 'static)>>)` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Jul 12 10:18:58.720 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Jul 12 10:18:58.720 INFO kablam!   --> tests/systems.rs:11:1
Jul 12 10:18:58.720 INFO kablam!    |
Jul 12 10:18:58.720 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 }
Jul 12 10:18:58.720 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 12 10:18:58.720 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.720 INFO kablam! 
Jul 12 10:18:58.734 INFO kablam! error[E0053]: method `run` has an incompatible type for trait
Jul 12 10:18:58.734 INFO kablam!  --> tests/events.rs:8:1
Jul 12 10:18:58.734 INFO kablam!   |
Jul 12 10:18:58.734 INFO kablam! 8 | event!(test_event, x: i64, y: i64 );
Jul 12 10:18:58.734 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Jul 12 10:18:58.734 INFO kablam!   |
Jul 12 10:18:58.734 INFO kablam!   = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec<shared_mutex::MappedSharedMutexReadGuard<'_, (dyn std::any::Any + 'static)>>, std::vec::Vec<shared_mutex::MappedSharedMutexWriteGuard<'_, (dyn std::any::Any + 'static)>>)` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Jul 12 10:18:58.734 INFO kablam!              found type `fn(&test_event::HandlerInstance, std::vec::Vec<shared_mutex::MappedSharedMutexReadGuard<'_, (dyn std::any::Any + 'static)>>, std::vec::Vec<shared_mutex::MappedSharedMutexWriteGuard<'_, (dyn std::any::Any + 'static)>>)` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Jul 12 10:18:58.735 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Jul 12 10:18:58.735 INFO kablam!  --> tests/events.rs:8:1
Jul 12 10:18:58.735 INFO kablam!   |
Jul 12 10:18:58.735 INFO kablam! 8 | event!(test_event, x: i64, y: i64 );
Jul 12 10:18:58.735 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 12 10:18:58.735 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.735 INFO kablam! 
Jul 12 10:18:58.735 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait
Jul 12 10:18:58.735 INFO kablam!   --> tests/systems.rs:17:2
Jul 12 10:18:58.735 INFO kablam!    |
Jul 12 10:18:58.736 INFO kablam! 17 |       component! { position,
Jul 12 10:18:58.736 INFO kablam!    |  _____^
Jul 12 10:18:58.736 INFO kablam! 18 | |         x: i64,
Jul 12 10:18:58.736 INFO kablam! 19 | |         y: i64
Jul 12 10:18:58.736 INFO kablam! 20 | |     }
Jul 12 10:18:58.736 INFO kablam!    | |_____^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Jul 12 10:18:58.736 INFO kablam!    |
Jul 12 10:18:58.736 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.736 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.736 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Jul 12 10:18:58.736 INFO kablam!   --> tests/systems.rs:17:2
Jul 12 10:18:58.736 INFO kablam!    |
Jul 12 10:18:58.736 INFO kablam! 17 |       component! { position,
Jul 12 10:18:58.736 INFO kablam!    |  _____^
Jul 12 10:18:58.736 INFO kablam! 18 | |         x: i64,
Jul 12 10:18:58.736 INFO kablam! 19 | |         y: i64
Jul 12 10:18:58.736 INFO kablam! 20 | |     }
Jul 12 10:18:58.736 INFO kablam!    | |_____^
Jul 12 10:18:58.736 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.736 INFO kablam! 
Jul 12 10:18:58.736 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait
Jul 12 10:18:58.736 INFO kablam!   --> tests/systems.rs:17:2
Jul 12 10:18:58.736 INFO kablam!    |
Jul 12 10:18:58.737 INFO kablam! 17 |       component! { position,
Jul 12 10:18:58.737 INFO kablam!    |  _____^
Jul 12 10:18:58.737 INFO kablam! 18 | |         x: i64,
Jul 12 10:18:58.737 INFO kablam! 19 | |         y: i64
Jul 12 10:18:58.737 INFO kablam! 20 | |     }
Jul 12 10:18:58.737 INFO kablam!    | |_____^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard`
Jul 12 10:18:58.737 INFO kablam!    |
Jul 12 10:18:58.737 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.737 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.737 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Jul 12 10:18:58.737 INFO kablam!   --> tests/systems.rs:17:2
Jul 12 10:18:58.737 INFO kablam!    |
Jul 12 10:18:58.737 INFO kablam! 17 |       component! { position,
Jul 12 10:18:58.737 INFO kablam!    |  _____^
Jul 12 10:18:58.737 INFO kablam! 18 | |         x: i64,
Jul 12 10:18:58.738 INFO kablam! 19 | |         y: i64
Jul 12 10:18:58.738 INFO kablam! 20 | |     }
Jul 12 10:18:58.738 INFO kablam!    | |_____^
Jul 12 10:18:58.738 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.738 INFO kablam! 
Jul 12 10:18:58.766 INFO kablam! error: aborting due to 4 previous errors
Jul 12 10:18:58.766 INFO kablam! 
Jul 12 10:18:58.766 INFO kablam! For more information about this error, try `rustc --explain E0053`.
Jul 12 10:18:58.780 INFO kablam! error: aborting due to previous error
Jul 12 10:18:58.780 INFO kablam! 
Jul 12 10:18:58.780 INFO kablam! For more information about this error, try `rustc --explain E0053`.
Jul 12 10:18:58.795 INFO kablam! error: Could not compile `entity_rust`.
Jul 12 10:18:58.795 INFO kablam! warning: build failed, waiting for other jobs to finish...
Jul 12 10:18:58.813 INFO kablam! error: Could not compile `entity_rust`.
Jul 12 10:18:58.813 INFO kablam! warning: build failed, waiting for other jobs to finish...
Jul 12 10:18:58.912 INFO kablam! error[E0053]: method `run` has an incompatible type for trait
Jul 12 10:18:58.912 INFO kablam!   --> tests/lib.rs:16:1
Jul 12 10:18:58.912 INFO kablam!    |
Jul 12 10:18:58.912 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 }
Jul 12 10:18:58.912 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Jul 12 10:18:58.912 INFO kablam!    |
Jul 12 10:18:58.912 INFO kablam!    = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec<shared_mutex::MappedSharedMutexReadGuard<'_, (dyn std::any::Any + 'static)>>, std::vec::Vec<shared_mutex::MappedSharedMutexWriteGuard<'_, (dyn std::any::Any + 'static)>>)` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Jul 12 10:18:58.912 INFO kablam!               found type `fn(&test_event::HandlerInstance, std::vec::Vec<shared_mutex::MappedSharedMutexReadGuard<'_, (dyn std::any::Any + 'static)>>, std::vec::Vec<shared_mutex::MappedSharedMutexWriteGuard<'_, (dyn std::any::Any + 'static)>>)` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Jul 12 10:18:58.913 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Jul 12 10:18:58.913 INFO kablam!   --> tests/lib.rs:16:1
Jul 12 10:18:58.913 INFO kablam!    |
Jul 12 10:18:58.913 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 }
Jul 12 10:18:58.913 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 12 10:18:58.913 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.913 INFO kablam! 
Jul 12 10:18:58.918 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait
Jul 12 10:18:58.918 INFO kablam!   --> tests/lib.rs:18:1
Jul 12 10:18:58.918 INFO kablam!    |
Jul 12 10:18:58.918 INFO kablam! 18 | component! { test_component, a: i64, b: i64 }
Jul 12 10:18:58.918 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Jul 12 10:18:58.918 INFO kablam!    |
Jul 12 10:18:58.919 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.919 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.919 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Jul 12 10:18:58.919 INFO kablam!   --> tests/lib.rs:18:1
Jul 12 10:18:58.919 INFO kablam!    |
Jul 12 10:18:58.919 INFO kablam! 18 | component! { test_component, a: i64, b: i64 }
Jul 12 10:18:58.919 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 12 10:18:58.919 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.919 INFO kablam! 
Jul 12 10:18:58.919 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait
Jul 12 10:18:58.919 INFO kablam!   --> tests/lib.rs:18:1
Jul 12 10:18:58.920 INFO kablam!    |
Jul 12 10:18:58.920 INFO kablam! 18 | component! { test_component, a: i64, b: i64 }
Jul 12 10:18:58.920 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard`
Jul 12 10:18:58.920 INFO kablam!    |
Jul 12 10:18:58.920 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.920 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.920 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Jul 12 10:18:58.920 INFO kablam!   --> tests/lib.rs:18:1
Jul 12 10:18:58.920 INFO kablam!    |
Jul 12 10:18:58.920 INFO kablam! 18 | component! { test_component, a: i64, b: i64 }
Jul 12 10:18:58.920 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jul 12 10:18:58.920 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.920 INFO kablam! 
Jul 12 10:18:58.928 INFO kablam! error: aborting due to 3 previous errors
Jul 12 10:18:58.928 INFO kablam! 
Jul 12 10:18:58.928 INFO kablam! For more information about this error, try `rustc --explain E0053`.
Jul 12 10:18:58.939 INFO kablam! error: Could not compile `entity_rust`.
Jul 12 10:18:58.939 INFO kablam! 
Jul 12 10:18:58.939 INFO kablam! To learn more, run the command again with --verbose.
Jul 12 10:18:58.949 INFO kablam! su: No module specific data is present
Jul 12 10:18:59.576 INFO running `"docker" "rm" "-f" "7cdc86cda88d2bd0cd371a4707758d9443f509e9fc8da0187a947f589205c057"`
Jul 12 10:18:59.743 INFO blam! 7cdc86cda88d2bd0cd371a4707758d9443f509e9fc8da0187a947f589205c057