Aug 30 18:58:27.828 INFO checking entity_rust-0.0.8 against master#ede55518431154bc761f7b2438cce9078c162700 for pr-53707 Aug 30 18:58:27.828 INFO running: cargo +ede55518431154bc761f7b2438cce9078c162700-alt check --frozen --all --all-targets Aug 30 18:58:27.828 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-3/pr-53707/master#ede55518431154bc761f7b2438cce9078c162700:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53707/worker-3/master#ede55518431154bc761f7b2438cce9078c162700:/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 +ede55518431154bc761f7b2438cce9078c162700-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Aug 30 18:58:28.022 INFO blam! f51abfc13dcf5706b0e1e0fd6a8988ff797ad2e030e143b3129fbef30640bf41 Aug 30 18:58:28.025 INFO running `"docker" "start" "-a" "f51abfc13dcf5706b0e1e0fd6a8988ff797ad2e030e143b3129fbef30640bf41"` Aug 30 18:58:28.799 INFO kablam! Compiling poison v0.1.0 Aug 30 18:58:28.800 INFO kablam! Checking uuid v0.6.5 Aug 30 18:58:29.686 INFO kablam! Checking shared-mutex v0.3.1 Aug 30 18:58:30.946 INFO kablam! Checking entity_rust v0.0.8 (file:///source) Aug 30 18:58:32.535 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Aug 30 18:58:32.535 INFO kablam! --> src/lib.rs:1:12 Aug 30 18:58:32.535 INFO kablam! | Aug 30 18:58:32.535 INFO kablam! 1 | #![feature(type_macros)] Aug 30 18:58:32.535 INFO kablam! | ^^^^^^^^^^^ Aug 30 18:58:32.535 INFO kablam! | Aug 30 18:58:32.535 INFO kablam! = note: #[warn(stable_features)] on by default Aug 30 18:58:32.535 INFO kablam! Aug 30 18:58:32.572 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Aug 30 18:58:32.572 INFO kablam! --> src/lib.rs:1:12 Aug 30 18:58:32.572 INFO kablam! | Aug 30 18:58:32.572 INFO kablam! 1 | #![feature(type_macros)] Aug 30 18:58:32.572 INFO kablam! | ^^^^^^^^^^^ Aug 30 18:58:32.572 INFO kablam! | Aug 30 18:58:32.572 INFO kablam! = note: #[warn(stable_features)] on by default Aug 30 18:58:32.572 INFO kablam! Aug 30 18:58:32.670 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Aug 30 18:58:32.670 INFO kablam! --> src/lib.rs:1:12 Aug 30 18:58:32.670 INFO kablam! | Aug 30 18:58:32.670 INFO kablam! 1 | #![feature(type_macros)] Aug 30 18:58:32.670 INFO kablam! | ^^^^^^^^^^^ Aug 30 18:58:32.670 INFO kablam! | Aug 30 18:58:32.670 INFO kablam! = note: #[warn(stable_features)] on by default Aug 30 18:58:32.670 INFO kablam! Aug 30 18:58:36.335 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Aug 30 18:58:36.335 INFO kablam! --> tests/components.rs:7:1 Aug 30 18:58:36.335 INFO kablam! | Aug 30 18:58:36.335 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Aug 30 18:58:36.336 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:58:36.336 INFO kablam! | Aug 30 18:58:36.336 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.336 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.336 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:58:36.336 INFO kablam! --> tests/components.rs:7:1 Aug 30 18:58:36.336 INFO kablam! | Aug 30 18:58:36.336 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Aug 30 18:58:36.336 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:58:36.336 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) Aug 30 18:58:36.336 INFO kablam! Aug 30 18:58:36.336 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Aug 30 18:58:36.336 INFO kablam! --> tests/components.rs:7:1 Aug 30 18:58:36.336 INFO kablam! | Aug 30 18:58:36.336 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Aug 30 18:58:36.336 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Aug 30 18:58:36.336 INFO kablam! | Aug 30 18:58:36.337 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:58:36.337 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:58:36.337 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:58:36.337 INFO kablam! --> tests/components.rs:7:1 Aug 30 18:58:36.337 INFO kablam! | Aug 30 18:58:36.337 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Aug 30 18:58:36.337 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:58:36.337 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) Aug 30 18:58:36.337 INFO kablam! Aug 30 18:58:36.360 INFO kablam! error: aborting due to 2 previous errors Aug 30 18:58:36.360 INFO kablam! Aug 30 18:58:36.361 INFO kablam! For more information about this error, try `rustc --explain E0053`. Aug 30 18:58:36.371 INFO kablam! error: Could not compile `entity_rust`. Aug 30 18:58:36.371 INFO kablam! warning: build failed, waiting for other jobs to finish... Aug 30 18:58:36.538 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Aug 30 18:58:36.538 INFO kablam! --> tests/systems.rs:10:1 Aug 30 18:58:36.538 INFO kablam! | Aug 30 18:58:36.538 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Aug 30 18:58:36.538 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:58:36.538 INFO kablam! | Aug 30 18:58:36.538 INFO kablam! = note: expected type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.538 INFO kablam! found type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.538 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:58:36.538 INFO kablam! --> tests/systems.rs:10:1 Aug 30 18:58:36.538 INFO kablam! | Aug 30 18:58:36.538 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Aug 30 18:58:36.538 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:58:36.538 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) Aug 30 18:58:36.538 INFO kablam! Aug 30 18:58:36.541 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Aug 30 18:58:36.541 INFO kablam! --> tests/systems.rs:11:1 Aug 30 18:58:36.541 INFO kablam! | Aug 30 18:58:36.541 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Aug 30 18:58:36.541 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:58:36.541 INFO kablam! | Aug 30 18:58:36.541 INFO kablam! = note: expected type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.541 INFO kablam! found type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.541 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:58:36.541 INFO kablam! --> tests/systems.rs:11:1 Aug 30 18:58:36.541 INFO kablam! | Aug 30 18:58:36.541 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Aug 30 18:58:36.541 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:58:36.541 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) Aug 30 18:58:36.541 INFO kablam! Aug 30 18:58:36.543 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Aug 30 18:58:36.543 INFO kablam! --> tests/systems.rs:17:2 Aug 30 18:58:36.543 INFO kablam! | Aug 30 18:58:36.543 INFO kablam! 17 | component! { position, Aug 30 18:58:36.544 INFO kablam! | _____^ Aug 30 18:58:36.544 INFO kablam! 18 | | x: i64, Aug 30 18:58:36.544 INFO kablam! 19 | | y: i64 Aug 30 18:58:36.544 INFO kablam! 20 | | } Aug 30 18:58:36.544 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:58:36.544 INFO kablam! | Aug 30 18:58:36.544 INFO kablam! = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.544 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.544 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:58:36.544 INFO kablam! --> tests/systems.rs:17:2 Aug 30 18:58:36.544 INFO kablam! | Aug 30 18:58:36.544 INFO kablam! 17 | component! { position, Aug 30 18:58:36.544 INFO kablam! | _____^ Aug 30 18:58:36.544 INFO kablam! 18 | | x: i64, Aug 30 18:58:36.544 INFO kablam! 19 | | y: i64 Aug 30 18:58:36.544 INFO kablam! 20 | | } Aug 30 18:58:36.544 INFO kablam! | |_____^ Aug 30 18:58:36.544 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) Aug 30 18:58:36.544 INFO kablam! Aug 30 18:58:36.544 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Aug 30 18:58:36.544 INFO kablam! --> tests/systems.rs:17:2 Aug 30 18:58:36.544 INFO kablam! | Aug 30 18:58:36.544 INFO kablam! 17 | component! { position, Aug 30 18:58:36.544 INFO kablam! | _____^ Aug 30 18:58:36.544 INFO kablam! 18 | | x: i64, Aug 30 18:58:36.544 INFO kablam! 19 | | y: i64 Aug 30 18:58:36.544 INFO kablam! 20 | | } Aug 30 18:58:36.544 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Aug 30 18:58:36.544 INFO kablam! | Aug 30 18:58:36.544 INFO kablam! = note: expected type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:58:36.545 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:58:36.545 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:58:36.545 INFO kablam! --> tests/systems.rs:17:2 Aug 30 18:58:36.545 INFO kablam! | Aug 30 18:58:36.545 INFO kablam! 17 | component! { position, Aug 30 18:58:36.545 INFO kablam! | _____^ Aug 30 18:58:36.545 INFO kablam! 18 | | x: i64, Aug 30 18:58:36.545 INFO kablam! 19 | | y: i64 Aug 30 18:58:36.545 INFO kablam! 20 | | } Aug 30 18:58:36.545 INFO kablam! | |_____^ Aug 30 18:58:36.545 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) Aug 30 18:58:36.545 INFO kablam! Aug 30 18:58:36.551 INFO kablam! error: aborting due to 4 previous errors Aug 30 18:58:36.551 INFO kablam! Aug 30 18:58:36.551 INFO kablam! For more information about this error, try `rustc --explain E0053`. Aug 30 18:58:36.559 INFO kablam! error: Could not compile `entity_rust`. Aug 30 18:58:36.559 INFO kablam! warning: build failed, waiting for other jobs to finish... Aug 30 18:58:36.665 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Aug 30 18:58:36.665 INFO kablam! --> tests/events.rs:8:1 Aug 30 18:58:36.665 INFO kablam! | Aug 30 18:58:36.665 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Aug 30 18:58:36.665 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:58:36.665 INFO kablam! | Aug 30 18:58:36.665 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.665 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.665 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:58:36.665 INFO kablam! --> tests/events.rs:8:1 Aug 30 18:58:36.665 INFO kablam! | Aug 30 18:58:36.665 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Aug 30 18:58:36.665 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:58:36.665 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) Aug 30 18:58:36.665 INFO kablam! Aug 30 18:58:36.673 INFO kablam! error: aborting due to previous error Aug 30 18:58:36.674 INFO kablam! Aug 30 18:58:36.674 INFO kablam! For more information about this error, try `rustc --explain E0053`. Aug 30 18:58:36.678 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Aug 30 18:58:36.678 INFO kablam! --> tests/lib.rs:16:1 Aug 30 18:58:36.678 INFO kablam! | Aug 30 18:58:36.678 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Aug 30 18:58:36.678 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:58:36.678 INFO kablam! | Aug 30 18:58:36.678 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.678 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.679 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:58:36.679 INFO kablam! --> tests/lib.rs:16:1 Aug 30 18:58:36.679 INFO kablam! | Aug 30 18:58:36.679 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Aug 30 18:58:36.679 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:58:36.679 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) Aug 30 18:58:36.679 INFO kablam! Aug 30 18:58:36.682 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Aug 30 18:58:36.682 INFO kablam! --> tests/lib.rs:18:1 Aug 30 18:58:36.682 INFO kablam! | Aug 30 18:58:36.682 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Aug 30 18:58:36.682 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Aug 30 18:58:36.682 INFO kablam! | Aug 30 18:58:36.682 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.682 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Aug 30 18:58:36.682 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:58:36.682 INFO kablam! --> tests/lib.rs:18:1 Aug 30 18:58:36.682 INFO kablam! | Aug 30 18:58:36.682 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Aug 30 18:58:36.682 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:58:36.682 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) Aug 30 18:58:36.682 INFO kablam! Aug 30 18:58:36.682 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Aug 30 18:58:36.682 INFO kablam! --> tests/lib.rs:18:1 Aug 30 18:58:36.682 INFO kablam! | Aug 30 18:58:36.682 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Aug 30 18:58:36.682 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Aug 30 18:58:36.682 INFO kablam! | Aug 30 18:58:36.683 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:58:36.683 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Aug 30 18:58:36.683 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Aug 30 18:58:36.683 INFO kablam! --> tests/lib.rs:18:1 Aug 30 18:58:36.683 INFO kablam! | Aug 30 18:58:36.683 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Aug 30 18:58:36.683 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 30 18:58:36.683 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) Aug 30 18:58:36.683 INFO kablam! Aug 30 18:58:36.686 INFO kablam! error: Could not compile `entity_rust`. Aug 30 18:58:36.687 INFO kablam! warning: build failed, waiting for other jobs to finish... Aug 30 18:58:36.690 INFO kablam! error: aborting due to 3 previous errors Aug 30 18:58:36.690 INFO kablam! Aug 30 18:58:36.690 INFO kablam! For more information about this error, try `rustc --explain E0053`. Aug 30 18:58:36.698 INFO kablam! error: Could not compile `entity_rust`. Aug 30 18:58:36.698 INFO kablam! Aug 30 18:58:36.698 INFO kablam! To learn more, run the command again with --verbose. Aug 30 18:58:36.700 INFO kablam! su: No module specific data is present Aug 30 18:58:37.341 INFO running `"docker" "rm" "-f" "f51abfc13dcf5706b0e1e0fd6a8988ff797ad2e030e143b3129fbef30640bf41"` Aug 30 18:58:37.440 INFO blam! f51abfc13dcf5706b0e1e0fd6a8988ff797ad2e030e143b3129fbef30640bf41