[INFO] crate grrs_rk 0.1.0 is already in cache
[INFO] checking grrs_rk-0.1.0 against master#6dee5f1126dfd5c9314ee5ae9d9eb010e35ef257 for pr-70872
[INFO] extracting crate grrs_rk 0.1.0 into /workspace/builds/worker-3/source
[INFO] validating manifest of crates.io crate grrs_rk 0.1.0 on toolchain 6dee5f1126dfd5c9314ee5ae9d9eb010e35ef257
[INFO] running `"/workspace/cargo-home/bin/cargo" "+6dee5f1126dfd5c9314ee5ae9d9eb010e35ef257" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started tweaking crates.io crate grrs_rk 0.1.0
[INFO] finished tweaking crates.io crate grrs_rk 0.1.0
[INFO] tweaked toml for crates.io crate grrs_rk 0.1.0 written to /workspace/builds/worker-3/source/Cargo.toml
[INFO] crate crates.io crate grrs_rk 0.1.0 already has a lockfile, it will not be regenerated
[INFO] running `"/workspace/cargo-home/bin/cargo" "+6dee5f1126dfd5c9314ee5ae9d9eb010e35ef257" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3/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=forbid" "-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" "+6dee5f1126dfd5c9314ee5ae9d9eb010e35ef257" "check" "--frozen" "--all" "--all-targets"`
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] [stdout] a424f747887aaf79322e0480959df13f75548c0bf88103871206f27d08d20a01
[INFO] running `"docker" "start" "-a" "a424f747887aaf79322e0480959df13f75548c0bf88103871206f27d08d20a01"`
[INFO] [stderr]    Compiling syn v1.0.11
[INFO] [stderr]     Checking number_prefix v0.3.0
[INFO] [stderr]     Checking clicolors-control v1.0.1
[INFO] [stderr]     Checking termios v0.3.1
[INFO] [stderr]     Checking float-cmp v0.5.3
[INFO] [stderr]     Checking env_logger v0.7.1
[INFO] [stderr]     Checking structopt v0.2.18
[INFO] [stderr]     Checking tempfile v3.1.0
[INFO] [stderr]     Checking predicates v1.0.2
[INFO] [stderr]     Checking console v0.9.1
[INFO] [stderr]     Checking indicatif v0.13.0
[INFO] [stderr]    Compiling synstructure v0.12.3
[INFO] [stderr]    Compiling serde_derive v1.0.104
[INFO] [stderr]    Compiling failure_derive v0.1.6
[INFO] [stderr]     Checking failure v0.1.6
[INFO] [stderr]     Checking exitfailure v0.5.1
[INFO] [stderr]     Checking grrs_rk v0.1.0 (/opt/rustwide/workdir)
[INFO] [stderr] warning: unused `std::result::Result` that must be used
[INFO] [stderr]  --> src/lib.rs:4:13
[INFO] [stderr]   |
[INFO] [stderr] 4 |             writeln!(writer, "{}", line);
[INFO] [stderr]   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: `#[warn(unused_must_use)]` on by default
[INFO] [stderr]   = note: this `Result` may be an `Err` variant, which should be handled
[INFO] [stderr]   = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr]     Checking serde v1.0.104
[INFO] [stderr]     Checking serde_json v1.0.44
[INFO] [stderr]     Checking escargot v0.5.0
[INFO] [stderr]     Checking assert_cmd v0.12.0
[INFO] [stderr] warning: unused `std::result::Result` that must be used
[INFO] [stderr]  --> src/lib.rs:4:13
[INFO] [stderr]   |
[INFO] [stderr] 4 |             writeln!(writer, "{}", line);
[INFO] [stderr]   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: `#[warn(unused_must_use)]` on by default
[INFO] [stderr]   = note: this `Result` may be an `Err` variant, which should be handled
[INFO] [stderr]   = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0433]: failed to resolve: use of undeclared type or module `grrs`
[INFO] [stderr]   --> tests/cli.rs:10:5
[INFO] [stderr]    |
[INFO] [stderr] 10 |     grrs::find_matches("lorem ipsum\ndolor sit amet", "lorem", &mut result);
[INFO] [stderr]    |     ^^^^ use of undeclared type or module `grrs`
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to previous error
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0433`.
[INFO] [stderr] error: could not compile `grrs_rk`.
[INFO] [stderr] 
[INFO] [stderr] To learn more, run the command again with --verbose.
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stderr] error: build failed
[INFO] running `"docker" "inspect" "a424f747887aaf79322e0480959df13f75548c0bf88103871206f27d08d20a01"`
[INFO] running `"docker" "rm" "-f" "a424f747887aaf79322e0480959df13f75548c0bf88103871206f27d08d20a01"`
[INFO] [stdout] a424f747887aaf79322e0480959df13f75548c0bf88103871206f27d08d20a01