Dec 01 22:15:53.822 INFO testing ca1ek/glyph-core against 1.30.1 for beta-1.31-5
Dec 01 22:15:53.823 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-2/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-5/1.30.1:/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.1 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"`
Dec 01 22:15:54.229 INFO [stdout] ad4c6eab4b05f83cb92674d78ba7ee7d30f20a0998a41e56f520489e915a85ff
Dec 01 22:15:54.233 INFO running `"docker" "start" "-a" "ad4c6eab4b05f83cb92674d78ba7ee7d30f20a0998a41e56f520489e915a85ff"`
Dec 01 22:15:55.274 INFO [stderr] usermod: no changes
Dec 01 22:15:55.329 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 22:15:55.329 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 22:15:55.329 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 22:15:55.329 INFO [stderr] files will be included as a binary target:
Dec 01 22:15:55.329 INFO [stderr] 
Dec 01 22:15:55.329 INFO [stderr] * /source/src/bin/plug_load.rs
Dec 01 22:15:55.329 INFO [stderr] * /source/src/bin/frontend.rs
Dec 01 22:15:55.329 INFO [stderr] 
Dec 01 22:15:55.329 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 22:15:55.329 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 22:15:55.329 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 22:15:55.329 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 22:15:55.329 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 22:15:55.330 INFO [stderr] 
Dec 01 22:15:55.330 INFO [stderr] For more information on this warning you can consult
Dec 01 22:15:55.330 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 22:15:55.417 INFO [stderr]    Compiling termion v1.4.0
Dec 01 22:15:55.417 INFO [stderr]    Compiling target_build_utils v0.3.1
Dec 01 22:15:58.271 INFO [stderr]    Compiling libloading v0.3.4
Dec 01 22:16:01.595 INFO [stderr]    Compiling editor v0.1.0 (/source)
Dec 01 22:16:02.171 INFO [stderr] error[E0554]: #![feature] may not be used on the stable release channel
Dec 01 22:16:02.171 INFO [stderr]  --> src/lib/lib.rs:1:1
Dec 01 22:16:02.171 INFO [stderr]   |
Dec 01 22:16:02.171 INFO [stderr] 1 | #![feature(box_syntax)]
Dec 01 22:16:02.171 INFO [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^
Dec 01 22:16:02.171 INFO [stderr] 
Dec 01 22:16:02.171 INFO [stderr] error: aborting due to previous error
Dec 01 22:16:02.171 INFO [stderr] 
Dec 01 22:16:02.171 INFO [stderr] For more information about this error, try `rustc --explain E0554`.
Dec 01 22:16:02.186 INFO [stderr] error: Could not compile `editor`.
Dec 01 22:16:02.186 INFO [stderr] 
Dec 01 22:16:02.186 INFO [stderr] To learn more, run the command again with --verbose.
Dec 01 22:16:02.186 INFO [stderr] su: No module specific data is present
Dec 01 22:16:02.780 INFO running `"docker" "inspect" "ad4c6eab4b05f83cb92674d78ba7ee7d30f20a0998a41e56f520489e915a85ff"`
Dec 01 22:16:03.013 INFO running `"docker" "rm" "-f" "ad4c6eab4b05f83cb92674d78ba7ee7d30f20a0998a41e56f520489e915a85ff"`
Dec 01 22:16:03.266 INFO [stdout] ad4c6eab4b05f83cb92674d78ba7ee7d30f20a0998a41e56f520489e915a85ff
