[INFO] crate deuterium_orm 0.5.0 is already in cache [INFO] checking deuterium_orm-0.5.0 against try#5e633973aa9255a88b65a39484627bb54e6044b3 for pr-66063 [INFO] extracting crate deuterium_orm 0.5.0 into /workspace/builds/worker-10/source [INFO] validating manifest of crates.io crate deuterium_orm 0.5.0 on toolchain 5e633973aa9255a88b65a39484627bb54e6044b3 [INFO] running `"/workspace/cargo-home/bin/cargo" "+5e633973aa9255a88b65a39484627bb54e6044b3" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started tweaking crates.io crate deuterium_orm 0.5.0 [INFO] removed 1 missing tests [INFO] finished tweaking crates.io crate deuterium_orm 0.5.0 [INFO] tweaked toml for crates.io crate deuterium_orm 0.5.0 written to /workspace/builds/worker-10/source/Cargo.toml [INFO] running `"/workspace/cargo-home/bin/cargo" "+5e633973aa9255a88b65a39484627bb54e6044b3" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/workspace/cargo-home/bin/cargo" "+5e633973aa9255a88b65a39484627bb54e6044b3" "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-10/source/tests/tests.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] running `"docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-10/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-10/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=allow" "-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" "+5e633973aa9255a88b65a39484627bb54e6044b3" "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] 9820fe4e59fb379c86f55d7cc926bcb26d5a3e76fe0f21eb07a1d6eb590de7c6 [INFO] running `"docker" "start" "-a" "9820fe4e59fb379c86f55d7cc926bcb26d5a3e76fe0f21eb07a1d6eb590de7c6"` [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/tests.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 arrayref v0.3.5 [INFO] [stderr] Checking fallible-iterator v0.1.6 [INFO] [stderr] Checking md5 v0.3.8 [INFO] [stderr] Compiling regex v0.2.11 [INFO] [stderr] Checking uuid v0.5.1 [INFO] [stderr] Compiling regex-syntax v0.4.2 [INFO] [stderr] Compiling num-bigint v0.2.3 [INFO] [stderr] Compiling num-iter v0.1.39 [INFO] [stderr] Compiling num-rational v0.2.2 [INFO] [stderr] Compiling num-complex v0.2.3 [INFO] [stderr] Checking stringprep v0.1.2 [INFO] [stderr] Checking iovec v0.1.4 [INFO] [stderr] Checking generic-array v0.9.0 [INFO] [stderr] Compiling time v0.1.42 [INFO] [stderr] Checking rand v0.3.23 [INFO] [stderr] Checking chrono v0.4.9 [INFO] [stderr] Checking parking_lot_core v0.6.2 [INFO] [stderr] Checking block-buffer v0.3.3 [INFO] [stderr] Checking bytes v0.4.12 [INFO] [stderr] Checking parking_lot v0.9.0 [INFO] [stderr] Checking digest v0.7.6 [INFO] [stderr] Checking crypto-mac v0.5.2 [INFO] [stderr] Checking sha2 v0.7.1 [INFO] [stderr] Checking hmac v0.5.0 [INFO] [stderr] error[E0554]: `#![feature]` may not be used on the beta release channel [INFO] [stderr] --> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/regex-0.2.11/src/lib.rs:522:34 [INFO] [stderr] | [INFO] [stderr] 522 | #![cfg_attr(feature = "pattern", feature(pattern))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] Checking scheduled-thread-pool v0.2.2 [INFO] [stderr] Checking postgres-protocol v0.3.2 [INFO] [stderr] Checking r2d2 v0.8.6 [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 `regex`. [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stderr] error: build failed [INFO] running `"docker" "inspect" "9820fe4e59fb379c86f55d7cc926bcb26d5a3e76fe0f21eb07a1d6eb590de7c6"` [INFO] running `"docker" "rm" "-f" "9820fe4e59fb379c86f55d7cc926bcb26d5a3e76fe0f21eb07a1d6eb590de7c6"` [INFO] [stdout] 9820fe4e59fb379c86f55d7cc926bcb26d5a3e76fe0f21eb07a1d6eb590de7c6