[INFO] updating cached repository tobybot11/prime-timeout [INFO] running `"git" "fetch" "--all"` [INFO] [stdout] Fetching origin [INFO] [stderr] From git://github.com/tobybot11/prime-timeout [INFO] [stderr] * branch HEAD -> FETCH_HEAD [INFO] running `"git" "clone" "work/cache/sources/gh/tobybot11/prime-timeout" "work/ex/beta-1.37-6/sources/1.36.0/gh/tobybot11/prime-timeout"` [INFO] [stderr] Cloning into 'work/ex/beta-1.37-6/sources/1.36.0/gh/tobybot11/prime-timeout'... [INFO] [stderr] done. [INFO] running `"git" "clone" "work/cache/sources/gh/tobybot11/prime-timeout" "work/ex/beta-1.37-6/sources/beta-2019-07-23/gh/tobybot11/prime-timeout"` [INFO] [stderr] Cloning into 'work/ex/beta-1.37-6/sources/beta-2019-07-23/gh/tobybot11/prime-timeout'... [INFO] [stderr] done. [INFO] running `"git" "rev-parse" "HEAD"` [INFO] [stdout] f01185d3c20479fed705194ccf2952253f4b9454 [INFO] sha for GitHub repo tobybot11/prime-timeout: f01185d3c20479fed705194ccf2952253f4b9454 [INFO] validating manifest of tobybot11/prime-timeout 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 tobybot11/prime-timeout 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 tobybot11/prime-timeout [INFO] finished frobbing tobybot11/prime-timeout [INFO] frobbed toml for tobybot11/prime-timeout written to work/ex/beta-1.37-6/sources/1.36.0/gh/tobybot11/prime-timeout/Cargo.toml [INFO] started frobbing tobybot11/prime-timeout [INFO] finished frobbing tobybot11/prime-timeout [INFO] frobbed toml for tobybot11/prime-timeout written to work/ex/beta-1.37-6/sources/beta-2019-07-23/gh/tobybot11/prime-timeout/Cargo.toml [INFO] crate tobybot11/prime-timeout 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] [stderr] Blocking waiting for file lock on package cache lock [INFO] [stderr] Blocking waiting for file lock on package cache lock [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] testing tobybot11/prime-timeout 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-3/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/gh/tobybot11/prime-timeout:/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] 7f4f55295c5222445c5ac764d0df518bf780e7d1b2b3d3ec5ddd257578051e8d [INFO] running `"docker" "start" "-a" "7f4f55295c5222445c5ac764d0df518bf780e7d1b2b3d3ec5ddd257578051e8d"` [INFO] [stderr] Compiling tokio-timer v0.1.2 [INFO] [stderr] Compiling futures-cpupool v0.1.8 [INFO] [stderr] Compiling prime-timeout 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(core_intrinsics)] [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 `prime-timeout`. [INFO] [stderr] [INFO] [stderr] To learn more, run the command again with --verbose. [INFO] running `"docker" "inspect" "7f4f55295c5222445c5ac764d0df518bf780e7d1b2b3d3ec5ddd257578051e8d"` [INFO] running `"docker" "rm" "-f" "7f4f55295c5222445c5ac764d0df518bf780e7d1b2b3d3ec5ddd257578051e8d"` [INFO] [stdout] 7f4f55295c5222445c5ac764d0df518bf780e7d1b2b3d3ec5ddd257578051e8d