Dec 08 00:37:26.840 INFO testing accel-mma84-0.2.0 against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514 Dec 08 00:37:26.840 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-5/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"` Dec 08 00:37:27.258 INFO [stdout] 0a481d6db61a7e8309d5d673b177c19e7f5e5284985fd834c8547294bf7dc2f5 Dec 08 00:37:27.260 INFO running `"docker" "start" "-a" "0a481d6db61a7e8309d5d673b177c19e7f5e5284985fd834c8547294bf7dc2f5"` Dec 08 00:37:28.616 INFO [stderr] usermod: no changes Dec 08 00:37:28.652 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 08 00:37:28.652 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 08 00:37:28.652 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 08 00:37:28.652 INFO [stderr] files will be included as a binary target: Dec 08 00:37:28.652 INFO [stderr] Dec 08 00:37:28.652 INFO [stderr] * /source/src/main.rs Dec 08 00:37:28.652 INFO [stderr] Dec 08 00:37:28.652 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 08 00:37:28.652 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 08 00:37:28.652 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 08 00:37:28.652 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 08 00:37:28.652 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 08 00:37:28.652 INFO [stderr] Dec 08 00:37:28.652 INFO [stderr] For more information on this warning you can consult Dec 08 00:37:28.652 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 08 00:37:28.652 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `tessel-accel`, Dec 08 00:37:28.652 INFO [stderr] please set bin.path in Cargo.toml Dec 08 00:37:28.695 INFO [stderr] Compiling accel-mma84 v0.2.0 (/source) Dec 08 00:37:29.345 INFO [stderr] error[E0463]: can't find crate for `alloc_system` Dec 08 00:37:29.345 INFO [stderr] --> src/lib.rs:2:1 Dec 08 00:37:29.345 INFO [stderr] | Dec 08 00:37:29.345 INFO [stderr] 2 | extern crate alloc_system; Dec 08 00:37:29.345 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ can't find crate Dec 08 00:37:29.345 INFO [stderr] Dec 08 00:37:29.356 INFO [stderr] error: aborting due to previous error Dec 08 00:37:29.356 INFO [stderr] Dec 08 00:37:29.356 INFO [stderr] For more information about this error, try `rustc --explain E0463`. Dec 08 00:37:29.356 INFO [stderr] error: Could not compile `accel-mma84`. Dec 08 00:37:29.356 INFO [stderr] Dec 08 00:37:29.356 INFO [stderr] To learn more, run the command again with --verbose. Dec 08 00:37:29.357 INFO [stderr] su: No module specific data is present Dec 08 00:37:30.262 INFO running `"docker" "inspect" "0a481d6db61a7e8309d5d673b177c19e7f5e5284985fd834c8547294bf7dc2f5"` Dec 08 00:37:30.581 INFO running `"docker" "rm" "-f" "0a481d6db61a7e8309d5d673b177c19e7f5e5284985fd834c8547294bf7dc2f5"` Dec 08 00:37:30.872 INFO [stdout] 0a481d6db61a7e8309d5d673b177c19e7f5e5284985fd834c8547294bf7dc2f5