[INFO] fetching crate eventsourcing 0.1.1... [INFO] checking eventsourcing-0.1.1 against try#ea663bba38739867a4b75ac820991b4f5d093c3b for pr-62262-1 [INFO] extracting crate eventsourcing 0.1.1 into /workspace/builds/worker-8/source [INFO] validating manifest of crates.io crate eventsourcing 0.1.1 on toolchain ea663bba38739867a4b75ac820991b4f5d093c3b [INFO] running `"/workspace/cargo-home/bin/cargo" "+ea663bba38739867a4b75ac820991b4f5d093c3b" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started tweaking crates.io crate eventsourcing 0.1.1 [INFO] removed 3 missing examples [INFO] finished tweaking crates.io crate eventsourcing 0.1.1 [INFO] tweaked toml for crates.io crate eventsourcing 0.1.1 written to /workspace/builds/worker-8/source/Cargo.toml [INFO] running `"/workspace/cargo-home/bin/cargo" "+ea663bba38739867a4b75ac820991b4f5d093c3b" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/workspace/cargo-home/bin/cargo" "+ea663bba38739867a4b75ac820991b4f5d093c3b" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] [stderr] warning: An explicit [[example]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other example targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a example target: [INFO] [stderr] [INFO] [stderr] * /workspace/builds/worker-8/source/examples/combat/main.rs [INFO] [stderr] * /workspace/builds/worker-8/source/examples/bank.rs [INFO] [stderr] * /workspace/builds/worker-8/source/examples/location.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 example target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autoexamples = 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-8/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-8/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" "+ea663bba38739867a4b75ac820991b4f5d093c3b" "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] 48ade5e9f5e6005c971afa3f4113d7c2bc3b6882b0b4449b488d6d0f1aca6b2a [INFO] running `"docker" "start" "-a" "48ade5e9f5e6005c971afa3f4113d7c2bc3b6882b0b4449b488d6d0f1aca6b2a"` [INFO] [stderr] warning: An explicit [[example]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other example targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a example target: [INFO] [stderr] [INFO] [stderr] * /opt/rustwide/workdir/examples/combat/main.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/bank.rs [INFO] [stderr] * /opt/rustwide/workdir/examples/location.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 example target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autoexamples = 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] Compiling proc-macro2 v0.2.3 [INFO] [stderr] Checking eventsourcing v0.1.1 (/opt/rustwide/workdir) [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/lib.rs:136:32 [INFO] [stderr] | [INFO] [stderr] 136 | fn cause(&self) -> Option<&std::error::Error> { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^ help: use `dyn`: `dyn std::error::Error` [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(bare_trait_objects)]` on by default [INFO] [stderr] [INFO] [stderr] Compiling quote v0.4.2 [INFO] [stderr] Compiling syn v0.12.15 [INFO] [stderr] Compiling eventsourcing-derive v0.1.1 [INFO] [stderr] warning: trait objects without an explicit `dyn` are deprecated [INFO] [stderr] --> src/lib.rs:136:32 [INFO] [stderr] | [INFO] [stderr] 136 | fn cause(&self) -> Option<&std::error::Error> { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^ help: use `dyn`: `dyn std::error::Error` [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(bare_trait_objects)]` on by default [INFO] [stderr] [INFO] [stderr] warning: the feature `attr_literals` has been stable since 1.30.0 and no longer requires an attribute to enable [INFO] [stderr] --> tests/cloudevents.rs:1:12 [INFO] [stderr] | [INFO] [stderr] 1 | #![feature(attr_literals)] [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(stable_features)]` on by default [INFO] [stderr] [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 10.09s [INFO] running `"docker" "inspect" "48ade5e9f5e6005c971afa3f4113d7c2bc3b6882b0b4449b488d6d0f1aca6b2a"` [INFO] running `"docker" "rm" "-f" "48ade5e9f5e6005c971afa3f4113d7c2bc3b6882b0b4449b488d6d0f1aca6b2a"` [INFO] [stdout] 48ade5e9f5e6005c971afa3f4113d7c2bc3b6882b0b4449b488d6d0f1aca6b2a