Nov 01 13:41:03.873 INFO testing ca1ek/glyph-core against 1.30.0 for beta-1.31-1
Nov 01 13:41:03.873 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-7/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/beta-1.31-1/1.30.0:/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 +1.30.0 build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 01 13:41:04.090 INFO blam! 0dc64d6b1c16cfa5336295c0c130e16bf74ce70cd803bfebfd990610e831384a
Nov 01 13:41:04.097 INFO running `"docker" "start" "-a" "0dc64d6b1c16cfa5336295c0c130e16bf74ce70cd803bfebfd990610e831384a"`
Nov 01 13:41:04.883 INFO kablam! usermod: no changes
Nov 01 13:41:04.932 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 01 13:41:04.932 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 01 13:41:04.932 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 01 13:41:04.932 INFO kablam! files will be included as a binary target:
Nov 01 13:41:04.932 INFO kablam! 
Nov 01 13:41:04.933 INFO kablam! * /source/src/bin/plug_load.rs
Nov 01 13:41:04.933 INFO kablam! * /source/src/bin/frontend.rs
Nov 01 13:41:04.933 INFO kablam! 
Nov 01 13:41:04.933 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 01 13:41:04.933 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 01 13:41:04.933 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 01 13:41:04.933 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 01 13:41:04.933 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 01 13:41:04.933 INFO kablam! 
Nov 01 13:41:04.933 INFO kablam! For more information on this warning you can consult
Nov 01 13:41:04.933 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 01 13:41:05.003 INFO kablam!    Compiling termion v1.4.0
Nov 01 13:41:05.007 INFO kablam!    Compiling target_build_utils v0.3.1
Nov 01 13:41:06.995 INFO kablam!    Compiling libloading v0.3.4
Nov 01 13:41:09.205 INFO kablam!    Compiling editor v0.1.0 (/source)
Nov 01 13:41:09.685 INFO kablam! error[E0554]: #![feature] may not be used on the stable release channel
Nov 01 13:41:09.685 INFO kablam!  --> src/lib/lib.rs:1:1
Nov 01 13:41:09.685 INFO kablam!   |
Nov 01 13:41:09.685 INFO kablam! 1 | #![feature(box_syntax)]
Nov 01 13:41:09.685 INFO kablam!   | ^^^^^^^^^^^^^^^^^^^^^^^
Nov 01 13:41:09.685 INFO kablam! 
Nov 01 13:41:09.685 INFO kablam! error: aborting due to previous error
Nov 01 13:41:09.685 INFO kablam! 
Nov 01 13:41:09.685 INFO kablam! For more information about this error, try `rustc --explain E0554`.
Nov 01 13:41:09.685 INFO kablam! error: Could not compile `editor`.
Nov 01 13:41:09.685 INFO kablam! 
Nov 01 13:41:09.685 INFO kablam! To learn more, run the command again with --verbose.
Nov 01 13:41:09.686 INFO kablam! su: No module specific data is present
Nov 01 13:41:10.167 INFO running `"docker" "rm" "-f" "0dc64d6b1c16cfa5336295c0c130e16bf74ce70cd803bfebfd990610e831384a"`
Nov 01 13:41:10.518 INFO blam! 0dc64d6b1c16cfa5336295c0c130e16bf74ce70cd803bfebfd990610e831384a
