Sep 01 21:42:54.100 INFO checking entity_rust-0.0.8 against try#aa245a5862056b681d2ccdb178f58891108cd3a6 for pr-53831 Sep 01 21:42:54.100 INFO running: cargo +aa245a5862056b681d2ccdb178f58891108cd3a6-alt check --frozen --all --all-targets Sep 01 21:42:54.101 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-3/pr-53831/try#aa245a5862056b681d2ccdb178f58891108cd3a6:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53831/worker-3/try#aa245a5862056b681d2ccdb178f58891108cd3a6:/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 +aa245a5862056b681d2ccdb178f58891108cd3a6-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:54.307 INFO blam! 9b3320973e4e9a8880228deb3e28976e3242f75b15a7fd05ae20d85bdd1d4917 Sep 01 21:42:54.309 INFO running `"docker" "start" "-a" "9b3320973e4e9a8880228deb3e28976e3242f75b15a7fd05ae20d85bdd1d4917"` Sep 01 21:42:55.552 INFO kablam! Compiling poison v0.1.0 Sep 01 21:42:55.555 INFO kablam! Compiling uuid v0.6.5 Sep 01 21:42:56.584 INFO kablam! Checking shared-mutex v0.3.1 Sep 01 21:42:58.525 INFO kablam! Checking entity_rust v0.0.8 (file:///source) Sep 01 21:43:00.392 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:00.393 INFO kablam! --> src/lib.rs:1:12 Sep 01 21:43:00.393 INFO kablam! | Sep 01 21:43:00.393 INFO kablam! 1 | #![feature(type_macros)] Sep 01 21:43:00.393 INFO kablam! | ^^^^^^^^^^^ Sep 01 21:43:00.393 INFO kablam! | Sep 01 21:43:00.393 INFO kablam! = note: #[warn(stable_features)] on by default Sep 01 21:43:00.394 INFO kablam! Sep 01 21:43:00.401 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:00.401 INFO kablam! --> src/lib.rs:1:12 Sep 01 21:43:00.401 INFO kablam! | Sep 01 21:43:00.401 INFO kablam! 1 | #![feature(type_macros)] Sep 01 21:43:00.401 INFO kablam! | ^^^^^^^^^^^ Sep 01 21:43:00.401 INFO kablam! | Sep 01 21:43:00.401 INFO kablam! = note: #[warn(stable_features)] on by default Sep 01 21:43:00.401 INFO kablam! Sep 01 21:43:00.632 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:00.632 INFO kablam! --> src/lib.rs:1:12 Sep 01 21:43:00.632 INFO kablam! | Sep 01 21:43:00.632 INFO kablam! 1 | #![feature(type_macros)] Sep 01 21:43:00.632 INFO kablam! | ^^^^^^^^^^^ Sep 01 21:43:00.632 INFO kablam! | Sep 01 21:43:00.633 INFO kablam! = note: #[warn(stable_features)] on by default Sep 01 21:43:00.633 INFO kablam! Sep 01 21:43:04.089 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 01 21:43:04.089 INFO kablam! --> tests/components.rs:7:1 Sep 01 21:43:04.089 INFO kablam! | Sep 01 21:43:04.089 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 01 21:43:04.090 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 01 21:43:04.090 INFO kablam! | Sep 01 21:43:04.090 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:04.090 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:04.090 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 01 21:43:04.091 INFO kablam! --> tests/components.rs:7:1 Sep 01 21:43:04.091 INFO kablam! | Sep 01 21:43:04.091 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 01 21:43:04.091 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 01 21:43:04.091 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:04.091 INFO kablam! Sep 01 21:43:04.091 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 01 21:43:04.091 INFO kablam! --> tests/components.rs:7:1 Sep 01 21:43:04.091 INFO kablam! | Sep 01 21:43:04.091 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 01 21:43:04.091 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 01 21:43:04.091 INFO kablam! | Sep 01 21:43:04.091 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:04.091 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:04.091 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 01 21:43:04.091 INFO kablam! --> tests/components.rs:7:1 Sep 01 21:43:04.091 INFO kablam! | Sep 01 21:43:04.091 INFO kablam! 7 | component! { test_component, a: i64, b: i64 } Sep 01 21:43:04.091 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 01 21:43:04.091 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:04.091 INFO kablam! Sep 01 21:43:04.113 INFO kablam! error: aborting due to 2 previous errors Sep 01 21:43:04.113 INFO kablam! Sep 01 21:43:04.113 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 01 21:43:04.121 INFO kablam! error: Could not compile `entity_rust`. Sep 01 21:43:04.122 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 01 21:43:04.424 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 01 21:43:04.424 INFO kablam! --> tests/systems.rs:10:1 Sep 01 21:43:04.424 INFO kablam! | Sep 01 21:43:04.424 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Sep 01 21:43:04.424 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 01 21:43:04.424 INFO kablam! | Sep 01 21:43:04.424 INFO kablam! = note: expected type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 01 21:43:04.424 INFO kablam! found type `fn(&my_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 01 21:43:04.425 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 01 21:43:04.425 INFO kablam! --> tests/systems.rs:10:1 Sep 01 21:43:04.425 INFO kablam! | Sep 01 21:43:04.425 INFO kablam! 10 | event!{ my_event , x: i64, y: i64 } Sep 01 21:43:04.425 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 01 21:43:04.425 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:04.425 INFO kablam! Sep 01 21:43:04.429 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 01 21:43:04.429 INFO kablam! --> tests/systems.rs:11:1 Sep 01 21:43:04.429 INFO kablam! | Sep 01 21:43:04.429 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Sep 01 21:43:04.429 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 01 21:43:04.429 INFO kablam! | Sep 01 21:43:04.429 INFO kablam! = note: expected type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 01 21:43:04.429 INFO kablam! found type `fn(&my_event_2::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 01 21:43:04.430 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 01 21:43:04.430 INFO kablam! --> tests/systems.rs:11:1 Sep 01 21:43:04.430 INFO kablam! | Sep 01 21:43:04.430 INFO kablam! 11 | event!{ my_event_2 , x: i64, y: i64 } Sep 01 21:43:04.430 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 01 21:43:04.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 01 21:43:04.430 INFO kablam! Sep 01 21:43:04.432 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 01 21:43:04.432 INFO kablam! --> tests/systems.rs:17:2 Sep 01 21:43:04.432 INFO kablam! | Sep 01 21:43:04.432 INFO kablam! 17 | component! { position, Sep 01 21:43:04.432 INFO kablam! | _____^ Sep 01 21:43:04.432 INFO kablam! 18 | | x: i64, Sep 01 21:43:04.432 INFO kablam! 19 | | y: i64 Sep 01 21:43:04.432 INFO kablam! 20 | | } Sep 01 21:43:04.432 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 01 21:43:04.432 INFO kablam! | Sep 01 21:43:04.433 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:04.433 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:04.433 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 01 21:43:04.433 INFO kablam! --> tests/systems.rs:17:2 Sep 01 21:43:04.433 INFO kablam! | Sep 01 21:43:04.433 INFO kablam! 17 | component! { position, Sep 01 21:43:04.433 INFO kablam! | _____^ Sep 01 21:43:04.434 INFO kablam! 18 | | x: i64, Sep 01 21:43:04.434 INFO kablam! 19 | | y: i64 Sep 01 21:43:04.434 INFO kablam! 20 | | } Sep 01 21:43:04.434 INFO kablam! | |_____^ Sep 01 21:43:04.434 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:04.434 INFO kablam! Sep 01 21:43:04.434 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 01 21:43:04.434 INFO kablam! --> tests/systems.rs:17:2 Sep 01 21:43:04.434 INFO kablam! | Sep 01 21:43:04.434 INFO kablam! 17 | component! { position, Sep 01 21:43:04.434 INFO kablam! | _____^ Sep 01 21:43:04.434 INFO kablam! 18 | | x: i64, Sep 01 21:43:04.434 INFO kablam! 19 | | y: i64 Sep 01 21:43:04.434 INFO kablam! 20 | | } Sep 01 21:43:04.434 INFO kablam! | |_____^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 01 21:43:04.434 INFO kablam! | Sep 01 21:43:04.434 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:04.434 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:04.434 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 01 21:43:04.434 INFO kablam! --> tests/systems.rs:17:2 Sep 01 21:43:04.434 INFO kablam! | Sep 01 21:43:04.434 INFO kablam! 17 | component! { position, Sep 01 21:43:04.434 INFO kablam! | _____^ Sep 01 21:43:04.434 INFO kablam! 18 | | x: i64, Sep 01 21:43:04.434 INFO kablam! 19 | | y: i64 Sep 01 21:43:04.434 INFO kablam! 20 | | } Sep 01 21:43:04.434 INFO kablam! | |_____^ Sep 01 21:43:04.435 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:04.435 INFO kablam! Sep 01 21:43:04.444 INFO kablam! error: aborting due to 4 previous errors Sep 01 21:43:04.444 INFO kablam! Sep 01 21:43:04.444 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 01 21:43:04.453 INFO kablam! error: Could not compile `entity_rust`. Sep 01 21:43:04.453 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 01 21:43:04.516 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 01 21:43:04.516 INFO kablam! --> tests/lib.rs:16:1 Sep 01 21:43:04.516 INFO kablam! | Sep 01 21:43:04.516 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Sep 01 21:43:04.516 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 01 21:43:04.516 INFO kablam! | Sep 01 21:43:04.516 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 01 21:43:04.516 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 01 21:43:04.516 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 01 21:43:04.516 INFO kablam! --> tests/lib.rs:16:1 Sep 01 21:43:04.516 INFO kablam! | Sep 01 21:43:04.516 INFO kablam! 16 | event!{ test_event , x: i64, y: i64 } Sep 01 21:43:04.516 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 01 21:43:04.516 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:04.516 INFO kablam! Sep 01 21:43:04.521 INFO kablam! error[E0053]: method `read_as_any` has an incompatible type for trait Sep 01 21:43:04.521 INFO kablam! --> tests/lib.rs:18:1 Sep 01 21:43:04.521 INFO kablam! | Sep 01 21:43:04.521 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 01 21:43:04.521 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 01 21:43:04.521 INFO kablam! | Sep 01 21:43:04.521 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:04.521 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:04.522 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 01 21:43:04.522 INFO kablam! --> tests/lib.rs:18:1 Sep 01 21:43:04.522 INFO kablam! | Sep 01 21:43:04.522 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 01 21:43:04.522 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 01 21:43:04.522 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:04.522 INFO kablam! Sep 01 21:43:04.522 INFO kablam! error[E0053]: method `write_as_any` has an incompatible type for trait Sep 01 21:43:04.522 INFO kablam! --> tests/lib.rs:18:1 Sep 01 21:43:04.522 INFO kablam! | Sep 01 21:43:04.522 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 01 21:43:04.522 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexWriteGuard`, found a different struct `shared_mutex::MappedSharedMutexWriteGuard` Sep 01 21:43:04.522 INFO kablam! | Sep 01 21:43:04.522 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:04.523 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:04.523 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 01 21:43:04.523 INFO kablam! --> tests/lib.rs:18:1 Sep 01 21:43:04.523 INFO kablam! | Sep 01 21:43:04.523 INFO kablam! 18 | component! { test_component, a: i64, b: i64 } Sep 01 21:43:04.523 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 01 21:43:04.523 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:04.523 INFO kablam! Sep 01 21:43:04.524 INFO kablam! error[E0053]: method `run` has an incompatible type for trait Sep 01 21:43:04.524 INFO kablam! --> tests/events.rs:8:1 Sep 01 21:43:04.524 INFO kablam! | Sep 01 21:43:04.524 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Sep 01 21:43:04.524 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `shared_mutex::MappedSharedMutexReadGuard`, found a different struct `shared_mutex::MappedSharedMutexReadGuard` Sep 01 21:43:04.524 INFO kablam! | Sep 01 21:43:04.524 INFO kablam! = note: expected type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 01 21:43:04.524 INFO kablam! found type `fn(&test_event::HandlerInstance, std::vec::Vec>, std::vec::Vec>)` (struct `shared_mutex::MappedSharedMutexReadGuard`) Sep 01 21:43:04.524 INFO kablam! note: Perhaps two different versions of crate `shared_mutex` are being used? Sep 01 21:43:04.524 INFO kablam! --> tests/events.rs:8:1 Sep 01 21:43:04.524 INFO kablam! | Sep 01 21:43:04.524 INFO kablam! 8 | event!(test_event, x: i64, y: i64 ); Sep 01 21:43:04.524 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 01 21:43:04.524 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:04.524 INFO kablam! Sep 01 21:43:04.532 INFO kablam! error: aborting due to previous error Sep 01 21:43:04.532 INFO kablam! Sep 01 21:43:04.532 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 01 21:43:04.533 INFO kablam! error: aborting due to 3 previous errors Sep 01 21:43:04.533 INFO kablam! Sep 01 21:43:04.533 INFO kablam! For more information about this error, try `rustc --explain E0053`. Sep 01 21:43:04.542 INFO kablam! error: Could not compile `entity_rust`. Sep 01 21:43:04.542 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 01 21:43:04.542 INFO kablam! error: Could not compile `entity_rust`. Sep 01 21:43:04.542 INFO kablam! warning: build failed, waiting for other jobs to finish... Sep 01 21:43:04.870 INFO kablam! error: build failed Sep 01 21:43:04.872 INFO kablam! su: No module specific data is present Sep 01 21:43:05.502 INFO running `"docker" "rm" "-f" "9b3320973e4e9a8880228deb3e28976e3242f75b15a7fd05ae20d85bdd1d4917"` Sep 01 21:43:05.630 INFO blam! 9b3320973e4e9a8880228deb3e28976e3242f75b15a7fd05ae20d85bdd1d4917