[INFO] updating cached repository binarybana/sudok [INFO] running `"git" "fetch" "--all"` [INFO] [stdout] Fetching origin [INFO] [stderr] From git://github.com/binarybana/sudok [INFO] [stderr] * branch HEAD -> FETCH_HEAD [INFO] running `"git" "clone" "work/cache/sources/gh/binarybana/sudok" "work/ex/beta-1.37-6/sources/1.36.0/gh/binarybana/sudok"` [INFO] [stderr] Cloning into 'work/ex/beta-1.37-6/sources/1.36.0/gh/binarybana/sudok'... [INFO] [stderr] done. [INFO] running `"git" "clone" "work/cache/sources/gh/binarybana/sudok" "work/ex/beta-1.37-6/sources/beta-2019-07-23/gh/binarybana/sudok"` [INFO] [stderr] Cloning into 'work/ex/beta-1.37-6/sources/beta-2019-07-23/gh/binarybana/sudok'... [INFO] [stderr] done. [INFO] running `"git" "rev-parse" "HEAD"` [INFO] [stdout] f6fa2f047974a83bf7c71b7f6b7f5e986ce2fc7a [INFO] sha for GitHub repo binarybana/sudok: f6fa2f047974a83bf7c71b7f6b7f5e986ce2fc7a [INFO] validating manifest of binarybana/sudok on toolchain 1.36.0 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] validating manifest of binarybana/sudok on toolchain beta-2019-07-23 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started frobbing binarybana/sudok [INFO] finished frobbing binarybana/sudok [INFO] frobbed toml for binarybana/sudok written to work/ex/beta-1.37-6/sources/1.36.0/gh/binarybana/sudok/Cargo.toml [INFO] started frobbing binarybana/sudok [INFO] finished frobbing binarybana/sudok [INFO] frobbed toml for binarybana/sudok written to work/ex/beta-1.37-6/sources/beta-2019-07-23/gh/binarybana/sudok/Cargo.toml [INFO] crate binarybana/sudok already has a lockfile, it will not be regenerated [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] testing binarybana/sudok against 1.36.0 for beta-1.37-6 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-6/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/gh/binarybana/sudok:/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.36.0" "build" "--frozen"` [INFO] [stdout] 024d693c6c290c6586910159f94dac46feb7ea4941a74869d80c490edacdb604 [INFO] running `"docker" "start" "-a" "024d693c6c290c6586910159f94dac46feb7ea4941a74869d80c490edacdb604"` [INFO] [stderr] Compiling rayon-core v1.3.0 [INFO] [stderr] Compiling either v1.4.0 [INFO] [stderr] Compiling num_cpus v1.7.0 [INFO] [stderr] Compiling rand v0.3.18 [INFO] [stderr] Compiling aho-corasick v0.6.4 [INFO] [stderr] Compiling thread_local v0.3.4 [INFO] [stderr] Compiling coco v0.1.1 [INFO] [stderr] Compiling regex v0.2.3 [INFO] [stderr] Compiling rayon v0.9.0 [INFO] [stderr] Compiling env_logger v0.4.3 [INFO] [stderr] Compiling sudok v0.1.0 (/opt/crater/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(nll)] [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 `sudok`. [INFO] [stderr] [INFO] [stderr] To learn more, run the command again with --verbose. [INFO] running `"docker" "inspect" "024d693c6c290c6586910159f94dac46feb7ea4941a74869d80c490edacdb604"` [INFO] running `"docker" "rm" "-f" "024d693c6c290c6586910159f94dac46feb7ea4941a74869d80c490edacdb604"` [INFO] [stdout] 024d693c6c290c6586910159f94dac46feb7ea4941a74869d80c490edacdb604