Sep 01 21:42:55.278 INFO checking entity_rust-0.0.8 against master#1114ab684fbad001c4e580326d8eb4d8c4e917d3 for pr-53831
Sep 01 21:42:55.278 INFO running: cargo +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets
Sep 01 21:42:55.278 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-2/pr-53831/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53831/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 01 21:42:55.483 INFO blam! 0ff0b6d62a43b319435617596eb1c52f68a0386b1d4d1e9908543b0cf6d710d0
Sep 01 21:42:55.485 INFO running `"docker" "start" "-a" "0ff0b6d62a43b319435617596eb1c52f68a0386b1d4d1e9908543b0cf6d710d0"`
Sep 01 21:42:56.771 INFO kablam!    Compiling poison v0.1.0
Sep 01 21:42:56.793 INFO kablam!     Checking uuid v0.6.5
Sep 01 21:42:57.866 INFO kablam!    Compiling shared-mutex v0.3.1
Sep 01 21:42:59.375 INFO kablam!     Checking entity_rust v0.0.8 (file:///source)
Sep 01 21:43:01.045 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable
Sep 01 21:43:01.046 INFO kablam!  --> src/lib.rs:1:12
Sep 01 21:43:01.046 INFO kablam!   |
Sep 01 21:43:01.046 INFO kablam! 1 | #![feature(type_macros)]
Sep 01 21:43:01.046 INFO kablam!   |            ^^^^^^^^^^^
Sep 01 21:43:01.046 INFO kablam!   |
Sep 01 21:43:01.046 INFO kablam!   = note: #[warn(stable_features)] on by default
Sep 01 21:43:01.047 INFO kablam! 
Sep 01 21:43:01.254 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable
Sep 01 21:43:01.254 INFO kablam!  --> src/lib.rs:1:12
Sep 01 21:43:01.254 INFO kablam!   |
Sep 01 21:43:01.254 INFO kablam! 1 | #![feature(type_macros)]
Sep 01 21:43:01.254 INFO kablam!   |            ^^^^^^^^^^^
Sep 01 21:43:01.254 INFO kablam!   |
Sep 01 21:43:01.254 INFO kablam!   = note: #[warn(stable_features)] on by default
Sep 01 21:43:01.255 INFO kablam! 
Sep 01 21:43:01.487 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable
Sep 01 21:43:01.488 INFO kablam!  --> src/lib.rs:1:12
Sep 01 21:43:01.488 INFO kablam!   |
Sep 01 21:43:01.488 INFO kablam! 1 | #![feature(type_macros)]
Sep 01 21:43:01.488 INFO kablam!   |            ^^^^^^^^^^^
Sep 01 21:43:01.488 INFO kablam!   |
Sep 01 21:43:01.488 INFO kablam!   = note: #[warn(stable_features)] on by default
Sep 01 21:43:01.488 INFO kablam! 
Sep 01 21:43:05.371 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait
Sep 01 21:43:05.371 INFO kablam!  --> tests/components.rs:7:1
Sep 01 21:43:05.372 INFO kablam!   |
Sep 01 21:43:05.372 INFO kablam! 7 | component! { test_component, a: i64, b: i64 }
Sep 01 21:43:05.372 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Sep 01 21:43:05.372 INFO kablam!   |
Sep 01 21:43:05.372 INFO kablam!   = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Sep 01 21:43:05.372 INFO kablam!              found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Sep 01 21:43:05.372 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Sep 01 21:43:05.372 INFO kablam!  --> tests/components.rs:7:1
Sep 01 21:43:05.372 INFO kablam!   |
Sep 01 21:43:05.372 INFO kablam! 7 | component! { test_component, a: i64, b: i64 }
Sep 01 21:43:05.372 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sep 01 21:43:05.372 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 01 21:43:05.372 INFO kablam! 
Sep 01 21:43:05.372 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait
Sep 01 21:43:05.373 INFO kablam!  --> tests/components.rs:7:1
Sep 01 21:43:05.373 INFO kablam!   |
Sep 01 21:43:05.373 INFO kablam! 7 | component! { test_component, a: i64, b: i64 }
Sep 01 21:43:05.373 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard`
Sep 01 21:43:05.373 INFO kablam!   |
Sep 01 21:43:05.373 INFO kablam!   = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`)
Sep 01 21:43:05.373 INFO kablam!              found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`)
Sep 01 21:43:05.373 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Sep 01 21:43:05.373 INFO kablam!  --> tests/components.rs:7:1
Sep 01 21:43:05.373 INFO kablam!   |
Sep 01 21:43:05.373 INFO kablam! 7 | component! { test_component, a: i64, b: i64 }
Sep 01 21:43:05.373 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sep 01 21:43:05.373 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 01 21:43:05.373 INFO kablam! 
Sep 01 21:43:05.395 INFO kablam! error: aborting due to 2 previous errors
Sep 01 21:43:05.395 INFO kablam! 
Sep 01 21:43:05.395 INFO kablam! For more information about this error, try `rustc --explain E0053`.
Sep 01 21:43:05.404 INFO kablam! error: Could not compile `entity_rust`.
Sep 01 21:43:05.404 INFO kablam! warning: build failed, waiting for other jobs to finish...
Sep 01 21:43:05.717 INFO kablam! error[E0053]: method `run` has an incompatible type for trait
Sep 01 21:43:05.717 INFO kablam!   --> tests/lib.rs:16:1
Sep 01 21:43:05.717 INFO kablam!    |
Sep 01 21:43:05.717 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 }
Sep 01 21:43:05.718 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Sep 01 21:43:05.719 INFO kablam!    |
Sep 01 21:43:05.720 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`)
Sep 01 21:43:05.720 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`)
Sep 01 21:43:05.720 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Sep 01 21:43:05.720 INFO kablam!   --> tests/lib.rs:16:1
Sep 01 21:43:05.720 INFO kablam!    |
Sep 01 21:43:05.720 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 }
Sep 01 21:43:05.720 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sep 01 21:43:05.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)
Sep 01 21:43:05.720 INFO kablam! 
Sep 01 21:43:05.724 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait
Sep 01 21:43:05.724 INFO kablam!   --> tests/lib.rs:18:1
Sep 01 21:43:05.724 INFO kablam!    |
Sep 01 21:43:05.724 INFO kablam! 18 | component! { test_component, a: i64, b: i64 }
Sep 01 21:43:05.725 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Sep 01 21:43:05.725 INFO kablam!    |
Sep 01 21:43:05.725 INFO kablam!    = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Sep 01 21:43:05.725 INFO kablam!               found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Sep 01 21:43:05.725 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Sep 01 21:43:05.725 INFO kablam!   --> tests/lib.rs:18:1
Sep 01 21:43:05.725 INFO kablam!    |
Sep 01 21:43:05.725 INFO kablam! 18 | component! { test_component, a: i64, b: i64 }
Sep 01 21:43:05.725 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sep 01 21:43:05.725 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 01 21:43:05.725 INFO kablam! 
Sep 01 21:43:05.725 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait
Sep 01 21:43:05.725 INFO kablam!   --> tests/lib.rs:18:1
Sep 01 21:43:05.725 INFO kablam!    |
Sep 01 21:43:05.725 INFO kablam! 18 | component! { test_component, a: i64, b: i64 }
Sep 01 21:43:05.725 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard`
Sep 01 21:43:05.725 INFO kablam!    |
Sep 01 21:43:05.725 INFO kablam!    = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`)
Sep 01 21:43:05.725 INFO kablam!               found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`)
Sep 01 21:43:05.725 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Sep 01 21:43:05.725 INFO kablam!   --> tests/lib.rs:18:1
Sep 01 21:43:05.725 INFO kablam!    |
Sep 01 21:43:05.725 INFO kablam! 18 | component! { test_component, a: i64, b: i64 }
Sep 01 21:43:05.725 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sep 01 21:43:05.725 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 01 21:43:05.726 INFO kablam! 
Sep 01 21:43:05.740 INFO kablam! error: aborting due to 3 previous errors
Sep 01 21:43:05.741 INFO kablam! 
Sep 01 21:43:05.741 INFO kablam! For more information about this error, try `rustc --explain E0053`.
Sep 01 21:43:05.749 INFO kablam! error: Could not compile `entity_rust`.
Sep 01 21:43:05.750 INFO kablam! warning: build failed, waiting for other jobs to finish...
Sep 01 21:43:05.921 INFO kablam! error[E0053]: method `run` has an incompatible type for trait
Sep 01 21:43:05.922 INFO kablam!  --> tests/events.rs:8:1
Sep 01 21:43:05.922 INFO kablam!   |
Sep 01 21:43:05.922 INFO kablam! 8 | event!(test_event, x: i64, y: i64 );
Sep 01 21:43:05.922 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Sep 01 21:43:05.922 INFO kablam!   |
Sep 01 21:43:05.922 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`)
Sep 01 21:43:05.922 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`)
Sep 01 21:43:05.922 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Sep 01 21:43:05.922 INFO kablam!  --> tests/events.rs:8:1
Sep 01 21:43:05.922 INFO kablam!   |
Sep 01 21:43:05.922 INFO kablam! 8 | event!(test_event, x: i64, y: i64 );
Sep 01 21:43:05.922 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sep 01 21:43:05.922 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 01 21:43:05.922 INFO kablam! 
Sep 01 21:43:05.930 INFO kablam! error: aborting due to previous error
Sep 01 21:43:05.931 INFO kablam! 
Sep 01 21:43:05.931 INFO kablam! For more information about this error, try `rustc --explain E0053`.
Sep 01 21:43:05.938 INFO kablam! error: Could not compile `entity_rust`.
Sep 01 21:43:05.938 INFO kablam! warning: build failed, waiting for other jobs to finish...
Sep 01 21:43:06.024 INFO kablam! error[E0053]: method `run` has an incompatible type for trait
Sep 01 21:43:06.024 INFO kablam!   --> tests/systems.rs:10:1
Sep 01 21:43:06.024 INFO kablam!    |
Sep 01 21:43:06.024 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 }
Sep 01 21:43:06.024 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Sep 01 21:43:06.024 INFO kablam!    |
Sep 01 21:43:06.024 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`)
Sep 01 21:43:06.024 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`)
Sep 01 21:43:06.024 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Sep 01 21:43:06.024 INFO kablam!   --> tests/systems.rs:10:1
Sep 01 21:43:06.024 INFO kablam!    |
Sep 01 21:43:06.024 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 }
Sep 01 21:43:06.024 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sep 01 21:43:06.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 01 21:43:06.025 INFO kablam! 
Sep 01 21:43:06.028 INFO kablam! error[E0053]: method `run` has an incompatible type for trait
Sep 01 21:43:06.028 INFO kablam!   --> tests/systems.rs:11:1
Sep 01 21:43:06.028 INFO kablam!    |
Sep 01 21:43:06.028 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 }
Sep 01 21:43:06.028 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Sep 01 21:43:06.028 INFO kablam!    |
Sep 01 21:43:06.028 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`)
Sep 01 21:43:06.028 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`)
Sep 01 21:43:06.029 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Sep 01 21:43:06.029 INFO kablam!   --> tests/systems.rs:11:1
Sep 01 21:43:06.029 INFO kablam!    |
Sep 01 21:43:06.029 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 }
Sep 01 21:43:06.029 INFO kablam!    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sep 01 21:43:06.029 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 01 21:43:06.029 INFO kablam! 
Sep 01 21:43:06.031 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait
Sep 01 21:43:06.031 INFO kablam!   --> tests/systems.rs:17:2
Sep 01 21:43:06.031 INFO kablam!    |
Sep 01 21:43:06.031 INFO kablam! 17 |       component! { position,
Sep 01 21:43:06.031 INFO kablam!    |  _____^
Sep 01 21:43:06.031 INFO kablam! 18 | |         x: i64,
Sep 01 21:43:06.031 INFO kablam! 19 | |         y: i64
Sep 01 21:43:06.032 INFO kablam! 20 | |     }
Sep 01 21:43:06.032 INFO kablam!    | |_____^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard`
Sep 01 21:43:06.032 INFO kablam!    |
Sep 01 21:43:06.032 INFO kablam!    = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Sep 01 21:43:06.032 INFO kablam!               found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`)
Sep 01 21:43:06.032 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Sep 01 21:43:06.032 INFO kablam!   --> tests/systems.rs:17:2
Sep 01 21:43:06.032 INFO kablam!    |
Sep 01 21:43:06.032 INFO kablam! 17 |       component! { position,
Sep 01 21:43:06.032 INFO kablam!    |  _____^
Sep 01 21:43:06.032 INFO kablam! 18 | |         x: i64,
Sep 01 21:43:06.032 INFO kablam! 19 | |         y: i64
Sep 01 21:43:06.032 INFO kablam! 20 | |     }
Sep 01 21:43:06.032 INFO kablam!    | |_____^
Sep 01 21:43:06.032 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 01 21:43:06.032 INFO kablam! 
Sep 01 21:43:06.032 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait
Sep 01 21:43:06.032 INFO kablam!   --> tests/systems.rs:17:2
Sep 01 21:43:06.032 INFO kablam!    |
Sep 01 21:43:06.032 INFO kablam! 17 |       component! { position,
Sep 01 21:43:06.032 INFO kablam!    |  _____^
Sep 01 21:43:06.032 INFO kablam! 18 | |         x: i64,
Sep 01 21:43:06.032 INFO kablam! 19 | |         y: i64
Sep 01 21:43:06.032 INFO kablam! 20 | |     }
Sep 01 21:43:06.032 INFO kablam!    | |_____^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard`
Sep 01 21:43:06.033 INFO kablam!    |
Sep 01 21:43:06.033 INFO kablam!    = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`)
Sep 01 21:43:06.033 INFO kablam!               found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`)
Sep 01 21:43:06.033 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used?
Sep 01 21:43:06.033 INFO kablam!   --> tests/systems.rs:17:2
Sep 01 21:43:06.033 INFO kablam!    |
Sep 01 21:43:06.033 INFO kablam! 17 |       component! { position,
Sep 01 21:43:06.033 INFO kablam!    |  _____^
Sep 01 21:43:06.033 INFO kablam! 18 | |         x: i64,
Sep 01 21:43:06.033 INFO kablam! 19 | |         y: i64
Sep 01 21:43:06.033 INFO kablam! 20 | |     }
Sep 01 21:43:06.033 INFO kablam!    | |_____^
Sep 01 21:43:06.033 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 01 21:43:06.033 INFO kablam! 
Sep 01 21:43:06.040 INFO kablam! error: aborting due to 4 previous errors
Sep 01 21:43:06.040 INFO kablam! 
Sep 01 21:43:06.041 INFO kablam! For more information about this error, try `rustc --explain E0053`.
Sep 01 21:43:06.049 INFO kablam! error: Could not compile `entity_rust`.
Sep 01 21:43:06.049 INFO kablam! 
Sep 01 21:43:06.049 INFO kablam! To learn more, run the command again with --verbose.
Sep 01 21:43:06.051 INFO kablam! su: No module specific data is present
Sep 01 21:43:06.781 INFO running `"docker" "rm" "-f" "0ff0b6d62a43b319435617596eb1c52f68a0386b1d4d1e9908543b0cf6d710d0"`
Sep 01 21:43:06.863 INFO blam! 0ff0b6d62a43b319435617596eb1c52f68a0386b1d4d1e9908543b0cf6d710d0