[INFO] crate teensy 0.1.0 is already in cache
[INFO] testing teensy-0.1.0 against 1.44.0 for beta-1.45-1
[INFO] extracting crate teensy 0.1.0 into /workspace/builds/worker-14/source
[INFO] validating manifest of crates.io crate teensy 0.1.0 on toolchain 1.44.0
[INFO] running `"/workspace/cargo-home/bin/cargo" "+1.44.0" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started tweaking crates.io crate teensy 0.1.0
[INFO] finished tweaking crates.io crate teensy 0.1.0
[INFO] tweaked toml for crates.io crate teensy 0.1.0 written to /workspace/builds/worker-14/source/Cargo.toml
[INFO] running `"/workspace/cargo-home/bin/cargo" "+1.44.0" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/workspace/cargo-home/bin/cargo" "+1.44.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other binary targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a binary target:
[INFO] [stderr] 
[INFO] [stderr] * /workspace/builds/worker-14/source/src/main.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobins = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr] warning: path `/workspace/builds/worker-14/source/src/main.rs` was erroneously implicitly accepted for binary `cargo-teensy`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] running `"docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-14/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-14/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=0" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+1.44.0" "build" "--frozen"`
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] [stdout] 3128878f7e0837dd0b4acef76709c619fc0110ac95e0195e57c854e1a782c325
[INFO] running `"docker" "start" "-a" "3128878f7e0837dd0b4acef76709c619fc0110ac95e0195e57c854e1a782c325"`
[INFO] [stderr] sudo: setrlimit(RLIMIT_CORE): Operation not permitted
[INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other binary targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a binary target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/rustwide/workdir/src/main.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobins = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr] warning: path `/opt/rustwide/workdir/src/main.rs` was erroneously implicitly accepted for binary `cargo-teensy`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]    Compiling strsim v0.5.2
[INFO] [stderr]    Compiling openssl-sys v0.7.17
[INFO] [stderr]    Compiling curl-sys v0.2.5
[INFO] [stderr]    Compiling toml v0.2.1
[INFO] [stderr]    Compiling docopt v0.6.86
[INFO] [stderr]    Compiling curl v0.3.11
[INFO] [stderr]    Compiling teensy v0.1.0 (/opt/rustwide/workdir)
[INFO] [stderr] error[E0554]: `#![feature]` may not be used on the stable release channel
[INFO] [stderr]  --> src/main.rs:1:1
[INFO] [stderr]   |
[INFO] [stderr] 1 | #![feature(btree_append)]
[INFO] [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated item 'try': use the `?` operator instead
[INFO] [stderr]    --> src/main.rs:163:17
[INFO] [stderr]     |
[INFO] [stderr] 163 |     let mut f = try!(File::open("Cargo.toml").map_err(|ioerr| format!("{:?}", ioerr)));
[INFO] [stderr]     |                 ^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: `#[warn(deprecated)]` on by default
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated item 'try': use the `?` operator instead
[INFO] [stderr]    --> src/main.rs:165:5
[INFO] [stderr]     |
[INFO] [stderr] 165 |     try!(f.read_to_string(&mut s).map_err(|ioerr| format!("{:?}", ioerr)));
[INFO] [stderr]     |     ^^^
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to previous error; 2 warnings emitted
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0554`.
[INFO] [stderr] error: could not compile `teensy`.
[INFO] [stderr] 
[INFO] [stderr] To learn more, run the command again with --verbose.
[INFO] running `"docker" "inspect" "3128878f7e0837dd0b4acef76709c619fc0110ac95e0195e57c854e1a782c325"`
[INFO] running `"docker" "rm" "-f" "3128878f7e0837dd0b4acef76709c619fc0110ac95e0195e57c854e1a782c325"`
[INFO] [stdout] 3128878f7e0837dd0b4acef76709c619fc0110ac95e0195e57c854e1a782c325