Sep 04 21:30:58.234 INFO checking entity_rust-0.0.8 against try#5fe695a3844714c70e8f7731a553f7947987a68a for pr-53913 Sep 04 21:30:58.234 INFO running: cargo +5fe695a3844714c70e8f7731a553f7947987a68a-alt check --frozen --all --all-targets Sep 04 21:30:58.234 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-2/pr-53913/try#5fe695a3844714c70e8f7731a553f7947987a68a:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53913/worker-2/try#5fe695a3844714c70e8f7731a553f7947987a68a:/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 +5fe695a3844714c70e8f7731a553f7947987a68a-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Sep 04 21:30:58.378 INFO blam! 346370cb010e3d275a350b3756dfd97bd44c7f91a958e6e9c6657d5a41fc5cae Sep 04 21:30:58.379 INFO running `"docker" "start" "-a" "346370cb010e3d275a350b3756dfd97bd44c7f91a958e6e9c6657d5a41fc5cae"` Sep 04 21:30:59.078 INFO kablam! Compiling poison v0.1.0 Sep 04 21:30:59.079 INFO kablam! Checking uuid v0.6.5 Sep 04 21:30:59.609 INFO kablam! Compiling shared-mutex v0.3.1 Sep 04 21:31:00.735 INFO kablam! Compiling entity_rust v0.0.8 (file:///source) Sep 04 21:31:02.406 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Sep 04 21:31:02.406 INFO kablam! --> src/lib.rs:1:12 Sep 04 21:31:02.406 INFO kablam! | Sep 04 21:31:02.406 INFO kablam! 1 | #![feature(type_macros)] Sep 04 21:31:02.406 INFO kablam! | ^^^^^^^^^^^ Sep 04 21:31:02.406 INFO kablam! | Sep 04 21:31:02.406 INFO kablam! = note: #[warn(stable_features)] on by default Sep 04 21:31:02.406 INFO kablam! Sep 04 21:31:02.450 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Sep 04 21:31:02.450 INFO kablam! --> src/lib.rs:1:12 Sep 04 21:31:02.451 INFO kablam! | Sep 04 21:31:02.451 INFO kablam! 1 | #![feature(type_macros)] Sep 04 21:31:02.451 INFO kablam! | ^^^^^^^^^^^ Sep 04 21:31:02.451 INFO kablam! | Sep 04 21:31:02.451 INFO kablam! = note: #[warn(stable_features)] on by default Sep 04 21:31:02.451 INFO kablam! Sep 04 21:31:02.468 INFO kablam! warning: the feature `type_macros` has been stable since 1.13.0 and no longer requires an attribute to enable Sep 04 21:31:02.468 INFO kablam! --> src/lib.rs:1:12 Sep 04 21:31:02.469 INFO kablam! | Sep 04 21:31:02.469 INFO kablam! 1 | #![feature(type_macros)] Sep 04 21:31:02.469 INFO kablam! | ^^^^^^^^^^^ Sep 04 21:31:02.469 INFO kablam! | Sep 04 21:31:02.469 INFO kablam! = note: #[warn(stable_features)] on by default Sep 04 21:31:02.469 INFO kablam! Sep 04 21:31:06.430 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 04 21:31:06.430 INFO kablam! --> tests/components.rs:7:1 Sep 04 21:31:06.430 INFO kablam! | Sep 04 21:31:06.430 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 04 21:31:06.430 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 21:31:06.430 INFO kablam! | Sep 04 21:31:06.430 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.430 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.430 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 21:31:06.430 INFO kablam! --> tests/components.rs:7:1 Sep 04 21:31:06.430 INFO kablam! | Sep 04 21:31:06.430 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 04 21:31:06.430 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 21:31:06.430 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 21:31:06.430 INFO kablam! Sep 04 21:31:06.430 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 04 21:31:06.430 INFO kablam! --> tests/components.rs:7:1 Sep 04 21:31:06.430 INFO kablam! | Sep 04 21:31:06.430 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 04 21:31:06.430 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 04 21:31:06.430 INFO kablam! | Sep 04 21:31:06.430 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 04 21:31:06.430 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 04 21:31:06.431 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 21:31:06.431 INFO kablam! --> tests/components.rs:7:1 Sep 04 21:31:06.431 INFO kablam! | Sep 04 21:31:06.431 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 04 21:31:06.431 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 21:31:06.431 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 21:31:06.431 INFO kablam! Sep 04 21:31:06.451 INFO kablam! error: aborting due to 2 previous errors Sep 04 21:31:06.451 INFO kablam! Sep 04 21:31:06.451 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 04 21:31:06.465 INFO kablam! error: Could not compile `entity_rust`. Sep 04 21:31:06.465 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 04 21:31:06.703 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 04 21:31:06.703 INFO kablam! --> tests/lib.rs:16:1 Sep 04 21:31:06.703 INFO kablam! | Sep 04 21:31:06.703 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Sep 04 21:31:06.703 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 21:31:06.703 INFO kablam! | Sep 04 21:31:06.704 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.704 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.704 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 21:31:06.704 INFO kablam! --> tests/lib.rs:16:1 Sep 04 21:31:06.704 INFO kablam! | Sep 04 21:31:06.704 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Sep 04 21:31:06.704 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 21:31:06.704 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 21:31:06.704 INFO kablam! Sep 04 21:31:06.711 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 04 21:31:06.711 INFO kablam! --> tests/lib.rs:18:1 Sep 04 21:31:06.711 INFO kablam! | Sep 04 21:31:06.711 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 04 21:31:06.711 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 21:31:06.711 INFO kablam! | Sep 04 21:31:06.712 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.712 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.712 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 21:31:06.712 INFO kablam! --> tests/lib.rs:18:1 Sep 04 21:31:06.712 INFO kablam! | Sep 04 21:31:06.712 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 04 21:31:06.712 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 21:31:06.713 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 21:31:06.713 INFO kablam! Sep 04 21:31:06.714 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 04 21:31:06.714 INFO kablam! --> tests/lib.rs:18:1 Sep 04 21:31:06.714 INFO kablam! | Sep 04 21:31:06.714 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 04 21:31:06.714 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 04 21:31:06.714 INFO kablam! | Sep 04 21:31:06.715 INFO kablam! = note: expected type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 04 21:31:06.715 INFO kablam! found type `fn(&test_component::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 04 21:31:06.715 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 21:31:06.715 INFO kablam! --> tests/lib.rs:18:1 Sep 04 21:31:06.715 INFO kablam! | Sep 04 21:31:06.715 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 04 21:31:06.715 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 21:31:06.716 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 21:31:06.716 INFO kablam! Sep 04 21:31:06.729 INFO kablam! error: aborting due to 3 previous errors Sep 04 21:31:06.729 INFO kablam! Sep 04 21:31:06.730 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 04 21:31:06.739 INFO kablam! error: Could not compile `entity_rust`. Sep 04 21:31:06.740 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 04 21:31:06.940 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 04 21:31:06.940 INFO kablam! --> tests/systems.rs:10:1 Sep 04 21:31:06.940 INFO kablam! | Sep 04 21:31:06.940 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Sep 04 21:31:06.940 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 21:31:06.940 INFO kablam! | Sep 04 21:31:06.940 INFO kablam! = note: expected type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.940 INFO kablam! found type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.941 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 21:31:06.941 INFO kablam! --> tests/systems.rs:10:1 Sep 04 21:31:06.941 INFO kablam! | Sep 04 21:31:06.941 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Sep 04 21:31:06.941 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 21:31:06.941 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 21:31:06.941 INFO kablam! Sep 04 21:31:06.944 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 04 21:31:06.944 INFO kablam! --> tests/systems.rs:11:1 Sep 04 21:31:06.944 INFO kablam! | Sep 04 21:31:06.944 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Sep 04 21:31:06.944 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 21:31:06.944 INFO kablam! | Sep 04 21:31:06.944 INFO kablam! = note: expected type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.944 INFO kablam! found type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.945 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 21:31:06.945 INFO kablam! --> tests/systems.rs:11:1 Sep 04 21:31:06.945 INFO kablam! | Sep 04 21:31:06.945 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Sep 04 21:31:06.945 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 21:31:06.945 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 21:31:06.945 INFO kablam! Sep 04 21:31:06.945 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 04 21:31:06.945 INFO kablam! --> tests/events.rs:8:1 Sep 04 21:31:06.945 INFO kablam! | Sep 04 21:31:06.945 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Sep 04 21:31:06.945 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 21:31:06.945 INFO kablam! | Sep 04 21:31:06.945 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.945 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.945 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 21:31:06.945 INFO kablam! --> tests/events.rs:8:1 Sep 04 21:31:06.945 INFO kablam! | Sep 04 21:31:06.945 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Sep 04 21:31:06.945 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 21:31:06.946 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 21:31:06.946 INFO kablam! Sep 04 21:31:06.947 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 04 21:31:06.947 INFO kablam! --> tests/systems.rs:17:2 Sep 04 21:31:06.947 INFO kablam! | Sep 04 21:31:06.947 INFO kablam! 17 | component! { position, Sep 04 21:31:06.947 INFO kablam! | _____^ Sep 04 21:31:06.947 INFO kablam! 18 | | x: i64, Sep 04 21:31:06.947 INFO kablam! 19 | | y: i64 Sep 04 21:31:06.947 INFO kablam! 20 | | } Sep 04 21:31:06.947 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 04 21:31:06.948 INFO kablam! | Sep 04 21:31:06.948 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 21:31:06.948 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexReadGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 04 21:31:06.948 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 21:31:06.948 INFO kablam! --> tests/systems.rs:17:2 Sep 04 21:31:06.948 INFO kablam! | Sep 04 21:31:06.948 INFO kablam! 17 | component! { position, Sep 04 21:31:06.948 INFO kablam! | _____^ Sep 04 21:31:06.948 INFO kablam! 18 | | x: i64, Sep 04 21:31:06.948 INFO kablam! 19 | | y: i64 Sep 04 21:31:06.948 INFO kablam! 20 | | } Sep 04 21:31:06.948 INFO kablam! | |_____^ Sep 04 21:31:06.948 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 21:31:06.948 INFO kablam! Sep 04 21:31:06.948 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 04 21:31:06.948 INFO kablam! --> tests/systems.rs:17:2 Sep 04 21:31:06.948 INFO kablam! | Sep 04 21:31:06.948 INFO kablam! 17 | component! { position, Sep 04 21:31:06.948 INFO kablam! | _____^ Sep 04 21:31:06.948 INFO kablam! 18 | | x: i64, Sep 04 21:31:06.948 INFO kablam! 19 | | y: i64 Sep 04 21:31:06.948 INFO kablam! 20 | | } Sep 04 21:31:06.948 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 04 21:31:06.948 INFO kablam! | Sep 04 21:31:06.948 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 21:31:06.948 INFO kablam! found type `fn(&my_system::position::ListGetters) -> shared_mutex::MappedSharedMutexWriteGuard<'mutex, (dyn std::any::Any + 'static)>` (struct `shared_mutex::MappedSharedMutexWriteGuard`) Sep 04 21:31:06.948 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 04 21:31:06.949 INFO kablam! --> tests/systems.rs:17:2 Sep 04 21:31:06.949 INFO kablam! | Sep 04 21:31:06.949 INFO kablam! 17 | component! { position, Sep 04 21:31:06.949 INFO kablam! | _____^ Sep 04 21:31:06.949 INFO kablam! 18 | | x: i64, Sep 04 21:31:06.949 INFO kablam! 19 | | y: i64 Sep 04 21:31:06.949 INFO kablam! 20 | | } Sep 04 21:31:06.949 INFO kablam! | |_____^ Sep 04 21:31:06.949 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 21:31:06.949 INFO kablam! Sep 04 21:31:06.954 INFO kablam! error: aborting due to previous error Sep 04 21:31:06.954 INFO kablam! Sep 04 21:31:06.955 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 04 21:31:06.958 INFO kablam! error: aborting due to 4 previous errors Sep 04 21:31:06.958 INFO kablam! Sep 04 21:31:06.958 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 04 21:31:06.964 INFO kablam! error: Could not compile `entity_rust`. Sep 04 21:31:06.964 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 04 21:31:06.967 INFO kablam! error: Could not compile `entity_rust`. Sep 04 21:31:06.967 INFO kablam! Sep 04 21:31:06.967 INFO kablam! To learn more, run the command again with --verbose. Sep 04 21:31:06.969 INFO kablam! su: No module specific data is present Sep 04 21:31:07.533 INFO running `"docker" "rm" "-f" "346370cb010e3d275a350b3756dfd97bd44c7f91a958e6e9c6657d5a41fc5cae"` Sep 04 21:31:07.695 INFO blam! 346370cb010e3d275a350b3756dfd97bd44c7f91a958e6e9c6657d5a41fc5cae