[INFO] updating cached repository WiSaGaN/perflab-rs
[INFO] running `"git" "fetch" "--all"`
[INFO] [stdout] Fetching origin
[INFO] [stderr] From git://github.com/WiSaGaN/perflab-rs
[INFO] [stderr]  * branch            HEAD       -> FETCH_HEAD
[INFO] running `"git" "clone" "work/cache/sources/gh/WiSaGaN/perflab-rs" "work/ex/beta-1.38-1/sources/1.37.0/gh/WiSaGaN/perflab-rs"`
[INFO] [stderr] Cloning into 'work/ex/beta-1.38-1/sources/1.37.0/gh/WiSaGaN/perflab-rs'...
[INFO] [stderr] done.
[INFO] running `"git" "clone" "work/cache/sources/gh/WiSaGaN/perflab-rs" "work/ex/beta-1.38-1/sources/beta-2019-08-13/gh/WiSaGaN/perflab-rs"`
[INFO] [stderr] Cloning into 'work/ex/beta-1.38-1/sources/beta-2019-08-13/gh/WiSaGaN/perflab-rs'...
[INFO] [stderr] done.
[INFO] running `"git" "rev-parse" "HEAD"`
[INFO] [stdout] a2288b5442d510d376d65b529cf8672a61b1c36a
[INFO] sha for GitHub repo WiSaGaN/perflab-rs: a2288b5442d510d376d65b529cf8672a61b1c36a
[INFO] validating manifest of WiSaGaN/perflab-rs on toolchain 1.37.0
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of WiSaGaN/perflab-rs on toolchain beta-2019-08-13
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing WiSaGaN/perflab-rs
[INFO] finished frobbing WiSaGaN/perflab-rs
[INFO] frobbed toml for WiSaGaN/perflab-rs written to work/ex/beta-1.38-1/sources/1.37.0/gh/WiSaGaN/perflab-rs/Cargo.toml
[INFO] started frobbing WiSaGaN/perflab-rs
[INFO] finished frobbing WiSaGaN/perflab-rs
[INFO] frobbed toml for WiSaGaN/perflab-rs written to work/ex/beta-1.38-1/sources/beta-2019-08-13/gh/WiSaGaN/perflab-rs/Cargo.toml
[INFO] crate WiSaGaN/perflab-rs already has a lockfile, it will not be regenerated
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.37.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-08-13" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] testing WiSaGaN/perflab-rs against 1.37.0 for beta-1.38-1
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.38-1/worker-0/1.37.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.38-1/sources/1.37.0/gh/WiSaGaN/perflab-rs:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.37.0" "build" "--frozen"`
[INFO] [stdout] 335d85291ea0e5d2444c965869e2f4dda4fa046d5488ebf1a5ec2b6354f941de
[INFO] running `"docker" "start" "-a" "335d85291ea0e5d2444c965869e2f4dda4fa046d5488ebf1a5ec2b6354f941de"`
[INFO] [stderr]    Compiling winapi v0.2.7
[INFO] [stderr]    Compiling libc v0.2.12
[INFO] [stderr]    Compiling kernel32-sys v0.2.2
[INFO] [stderr]    Compiling time v0.1.35
[INFO] [stderr]    Compiling perflab-rs v0.1.0 (/opt/crater/workdir)
[INFO] [stderr] error[E0554]: #![feature] may not be used on the stable release channel
[INFO] [stderr]  --> src/lib.rs:1:1
[INFO] [stderr]   |
[INFO] [stderr] 1 | #![feature(test)]
[INFO] [stderr]   | ^^^^^^^^^^^^^^^^^
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to previous error
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0554`.
[INFO] [stderr] error: Could not compile `perflab-rs`.
[INFO] [stderr] 
[INFO] [stderr] To learn more, run the command again with --verbose.
[INFO] running `"docker" "inspect" "335d85291ea0e5d2444c965869e2f4dda4fa046d5488ebf1a5ec2b6354f941de"`
[INFO] running `"docker" "rm" "-f" "335d85291ea0e5d2444c965869e2f4dda4fa046d5488ebf1a5ec2b6354f941de"`
[INFO] [stdout] 335d85291ea0e5d2444c965869e2f4dda4fa046d5488ebf1a5ec2b6354f941de