[INFO] crate factory_steel_derive 0.1.0 is already in cache
[INFO] checking factory_steel_derive-0.1.0 against try#d27c6c6a469a28343396a8f3ac1c9d403aabda69 for pr-66037
[INFO] extracting crate factory_steel_derive 0.1.0 into /workspace/builds/worker-14/source
[INFO] validating manifest of crates.io crate factory_steel_derive 0.1.0 on toolchain d27c6c6a469a28343396a8f3ac1c9d403aabda69
[INFO] running `"/workspace/cargo-home/bin/cargo" "+d27c6c6a469a28343396a8f3ac1c9d403aabda69" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started tweaking crates.io crate factory_steel_derive 0.1.0
[INFO] removed 0 missing tests
[INFO] finished tweaking crates.io crate factory_steel_derive 0.1.0
[INFO] tweaked toml for crates.io crate factory_steel_derive 0.1.0 written to /workspace/builds/worker-14/source/Cargo.toml
[INFO] running `"/workspace/cargo-home/bin/cargo" "+d27c6c6a469a28343396a8f3ac1c9d403aabda69" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/workspace/cargo-home/bin/cargo" "+d27c6c6a469a28343396a8f3ac1c9d403aabda69" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other test targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a test target:
[INFO] [stderr] 
[INFO] [stderr] * /workspace/builds/worker-14/source/tests/factory.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 test target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autotests = 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]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] running `"docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-14/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-14/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" "+d27c6c6a469a28343396a8f3ac1c9d403aabda69" "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] d74ecf74f6de89cabc37d82cb1f504fec30a5f1be5f3f0782348bfbf6b5331ad
[INFO] running `"docker" "start" "-a" "d74ecf74f6de89cabc37d82cb1f504fec30a5f1be5f3f0782348bfbf6b5331ad"`
[INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other test targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a test target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/rustwide/workdir/tests/factory.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 test target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autotests = 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]     Checking proc-macro2 v0.3.8
[INFO] [stderr]    Compiling quote v0.5.2
[INFO] [stderr]    Compiling syn v0.13.11
[INFO] [stderr]     Checking factory_steel_derive v0.1.0 (/opt/rustwide/workdir)
[INFO] [stderr] warning: unused `#[macro_use]` import
[INFO] [stderr]  --> src/lib.rs:5:1
[INFO] [stderr]   |
[INFO] [stderr] 5 | #[macro_use]
[INFO] [stderr]   | ^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: `#[warn(unused_imports)]` on by default
[INFO] [stderr] 
[INFO] [stderr] warning: unused `#[macro_use]` import
[INFO] [stderr]  --> src/lib.rs:5:1
[INFO] [stderr]   |
[INFO] [stderr] 5 | #[macro_use]
[INFO] [stderr]   | ^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: `#[warn(unused_imports)]` on by default
[INFO] [stderr] 
[INFO] [stderr] warning: unused `#[macro_use]` import
[INFO] [stderr]  --> src/lib.rs:5:1
[INFO] [stderr]   |
[INFO] [stderr] 5 | #[macro_use]
[INFO] [stderr]   | ^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: `#[warn(unused_imports)]` on by default
[INFO] [stderr] 
[INFO] [stderr] error[E0463]: can't find crate for `factory_steel`
[INFO] [stderr]  --> tests/tests.rs:2:1
[INFO] [stderr]   |
[INFO] [stderr] 2 | extern crate factory_steel;
[INFO] [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't find crate
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to previous error
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0463`.
[INFO] [stderr] error: could not compile `factory_steel_derive`.
[INFO] [stderr] 
[INFO] [stderr] To learn more, run the command again with --verbose.
[INFO] running `"docker" "inspect" "d74ecf74f6de89cabc37d82cb1f504fec30a5f1be5f3f0782348bfbf6b5331ad"`
[INFO] running `"docker" "rm" "-f" "d74ecf74f6de89cabc37d82cb1f504fec30a5f1be5f3f0782348bfbf6b5331ad"`
[INFO] [stdout] d74ecf74f6de89cabc37d82cb1f504fec30a5f1be5f3f0782348bfbf6b5331ad