[INFO] cloning repository Fishrock123/nucleus-chakra
[INFO] running `"git" "clone" "--bare" "git://github.com/Fishrock123/nucleus-chakra.git" "work/cache/sources/gh/Fishrock123/nucleus-chakra"`
[INFO] [stderr] Cloning into bare repository 'work/cache/sources/gh/Fishrock123/nucleus-chakra'...
[INFO] running `"git" "clone" "work/cache/sources/gh/Fishrock123/nucleus-chakra" "work/ex/pr-61874/sources/master#9f06855064ed06a50c496577b21ca50f92a2e67d/gh/Fishrock123/nucleus-chakra"`
[INFO] [stderr] Cloning into 'work/ex/pr-61874/sources/master#9f06855064ed06a50c496577b21ca50f92a2e67d/gh/Fishrock123/nucleus-chakra'...
[INFO] [stderr] done.
[INFO] running `"git" "clone" "work/cache/sources/gh/Fishrock123/nucleus-chakra" "work/ex/pr-61874/sources/try#d3301713b54af69ca9de941a8c6b0d8287dbd6df/gh/Fishrock123/nucleus-chakra"`
[INFO] [stderr] Cloning into 'work/ex/pr-61874/sources/try#d3301713b54af69ca9de941a8c6b0d8287dbd6df/gh/Fishrock123/nucleus-chakra'...
[INFO] [stderr] done.
[INFO] running `"git" "rev-parse" "HEAD"`
[INFO] [stdout] 90d4a5440cc43df0bb08fae2e3b972919b6bcae2
[INFO] sha for GitHub repo Fishrock123/nucleus-chakra: 90d4a5440cc43df0bb08fae2e3b972919b6bcae2
[INFO] validating manifest of Fishrock123/nucleus-chakra on toolchain master#9f06855064ed06a50c496577b21ca50f92a2e67d
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+9f06855064ed06a50c496577b21ca50f92a2e67d-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of Fishrock123/nucleus-chakra on toolchain try#d3301713b54af69ca9de941a8c6b0d8287dbd6df
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+d3301713b54af69ca9de941a8c6b0d8287dbd6df-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing Fishrock123/nucleus-chakra
[INFO] finished frobbing Fishrock123/nucleus-chakra
[INFO] frobbed toml for Fishrock123/nucleus-chakra written to work/ex/pr-61874/sources/master#9f06855064ed06a50c496577b21ca50f92a2e67d/gh/Fishrock123/nucleus-chakra/Cargo.toml
[INFO] started frobbing Fishrock123/nucleus-chakra
[INFO] finished frobbing Fishrock123/nucleus-chakra
[INFO] frobbed toml for Fishrock123/nucleus-chakra written to work/ex/pr-61874/sources/try#d3301713b54af69ca9de941a8c6b0d8287dbd6df/gh/Fishrock123/nucleus-chakra/Cargo.toml
[INFO] crate Fishrock123/nucleus-chakra already has a lockfile, it will not be regenerated
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+9f06855064ed06a50c496577b21ca50f92a2e67d-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded zip v0.1.18
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+d3301713b54af69ca9de941a8c6b0d8287dbd6df-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] checking Fishrock123/nucleus-chakra against try#d3301713b54af69ca9de941a8c6b0d8287dbd6df for pr-61874
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-61874/worker-3/try#d3301713b54af69ca9de941a8c6b0d8287dbd6df:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-61874/sources/try#d3301713b54af69ca9de941a8c6b0d8287dbd6df/gh/Fishrock123/nucleus-chakra:/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=forbid" "-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" "+d3301713b54af69ca9de941a8c6b0d8287dbd6df-alt" "check" "--frozen" "--all" "--all-targets"`
[INFO] [stdout] fcf0e443286da468a21c4208892848dc45f3913b957315d35cb2fec8d1a1c675
[INFO] running `"docker" "start" "-a" "fcf0e443286da468a21c4208892848dc45f3913b957315d35cb2fec8d1a1c675"`
[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/crater/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/crater/workdir/src/nucleus.rs` was erroneously implicitly accepted for binary `nucleus`,
[INFO] [stderr] please set bin.path in Cargo.toml
[INFO] [stderr]    Compiling miniz-sys v0.1.7
[INFO] [stderr]    Compiling bzip2-sys v0.1.4
[INFO] [stderr]    Compiling nucleus-chakra v0.0.0 (/opt/crater/workdir)
[INFO] [stderr]     Checking msdos_time v0.1.4
[INFO] [stderr] warning: unused import: `std::env`
[INFO] [stderr]  --> build.rs:8:5
[INFO] [stderr]   |
[INFO] [stderr] 8 | use std::env;
[INFO] [stderr]   |     ^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: #[warn(unused_imports)] on by default
[INFO] [stderr] 
[INFO] [stderr]     Checking flate2 v0.2.14
[INFO] [stderr]     Checking bzip2 v0.3.0
[INFO] [stderr]     Checking zip v0.1.18
[INFO] [stderr] error[E0432]: unresolved import `duk_structs`
[INFO] [stderr]  --> src/nucleus.rs:6:5
[INFO] [stderr]   |
[INFO] [stderr] 6 | use duk_structs::duk_context;
[INFO] [stderr]   |     ^^^^^^^^^^^ maybe a missing `extern crate duk_structs;`?
[INFO] [stderr] 
[INFO] [stderr] error[E0432]: unresolved import `duk_api`
[INFO] [stderr]  --> src/nucleus.rs:7:5
[INFO] [stderr]   |
[INFO] [stderr] 7 | use duk_api as duk;
[INFO] [stderr]   |     ^^^^^^^^^^^^^^ no `duk_api` in the root
[INFO] [stderr] 
[INFO] [stderr] error[E0432]: unresolved import `nucleus_functions`
[INFO] [stderr]  --> src/nucleus.rs:8:5
[INFO] [stderr]   |
[INFO] [stderr] 8 | use nucleus_functions;
[INFO] [stderr]   |     ^^^^^^^^^^^^^^^^^ no `nucleus_functions` in the root
[INFO] [stderr] 
[INFO] [stderr] error[E0601]: `main` function not found in crate `nucleus`
[INFO] [stderr]   |
[INFO] [stderr]   = note: consider adding a `main` function to `src/nucleus.rs`
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 4 previous errors
[INFO] [stderr] 
[INFO] [stderr] Some errors have detailed explanations: E0432, E0601.
[INFO] [stderr] For more information about an error, try `rustc --explain E0432`.
[INFO] [stderr] error: Could not compile `nucleus-chakra`.
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stderr] error[E0432]: unresolved import `duk_structs`
[INFO] [stderr]  --> src/nucleus.rs:6:5
[INFO] [stderr]   |
[INFO] [stderr] 6 | use duk_structs::duk_context;
[INFO] [stderr]   |     ^^^^^^^^^^^ maybe a missing `extern crate duk_structs;`?
[INFO] [stderr] 
[INFO] [stderr] error[E0432]: unresolved import `duk_api`
[INFO] [stderr]  --> src/nucleus.rs:7:5
[INFO] [stderr]   |
[INFO] [stderr] 7 | use duk_api as duk;
[INFO] [stderr]   |     ^^^^^^^^^^^^^^ no `duk_api` in the root
[INFO] [stderr] 
[INFO] [stderr] error[E0432]: unresolved import `nucleus_functions`
[INFO] [stderr]  --> src/nucleus.rs:8:5
[INFO] [stderr]   |
[INFO] [stderr] 8 | use nucleus_functions;
[INFO] [stderr]   |     ^^^^^^^^^^^^^^^^^ no `nucleus_functions` in the root
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 3 previous errors
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0432`.
[INFO] [stderr] error: Could not compile `nucleus-chakra`.
[INFO] [stderr] 
[INFO] [stderr] To learn more, run the command again with --verbose.
[INFO] running `"docker" "inspect" "fcf0e443286da468a21c4208892848dc45f3913b957315d35cb2fec8d1a1c675"`
[INFO] running `"docker" "rm" "-f" "fcf0e443286da468a21c4208892848dc45f3913b957315d35cb2fec8d1a1c675"`
[INFO] [stdout] fcf0e443286da468a21c4208892848dc45f3913b957315d35cb2fec8d1a1c675