[INFO] fetching crate rocket 0.5.1... [INFO] testing rocket-0.5.1 against master#d98a5da813da67eb189387b8ccfb73cf481275d8+rustflags=-Copt-level=3 for pr-138759 [INFO] extracting crate rocket 0.5.1 into /workspace/builds/worker-7-tc1/source [INFO] started tweaking crates.io crate rocket 0.5.1 [INFO] removed 0 missing tests [INFO] finished tweaking crates.io crate rocket 0.5.1 [INFO] tweaked toml for crates.io crate rocket 0.5.1 written to /workspace/builds/worker-7-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate rocket 0.5.1 on toolchain d98a5da813da67eb189387b8ccfb73cf481275d8 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 237 packages to latest compatible versions [INFO] [stderr] Adding atomic v0.5.3 (available: v0.6.1) [INFO] [stderr] Adding rand v0.8.5 (available: v0.9.2) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded der-parser v7.0.0 [INFO] [stderr] Downloaded asn1-rs-impl v0.1.0 [INFO] [stderr] Downloaded oid-registry v0.4.0 [INFO] [stderr] Downloaded asn1-rs-derive v0.1.0 [INFO] [stderr] Downloaded asn1-rs v0.3.1 [INFO] [stderr] Downloaded x509-parser v0.13.2 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/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" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 5a73f5e004df9beae61fa48bb9e7010bb7ce4e587e654ef9c1ee22e44db4b5c4 [INFO] running `Command { std: "docker" "start" "-a" "5a73f5e004df9beae61fa48bb9e7010bb7ce4e587e654ef9c1ee22e44db4b5c4", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "5a73f5e004df9beae61fa48bb9e7010bb7ce4e587e654ef9c1ee22e44db4b5c4", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "5a73f5e004df9beae61fa48bb9e7010bb7ce4e587e654ef9c1ee22e44db4b5c4", kill_on_drop: false }` [INFO] [stdout] 5a73f5e004df9beae61fa48bb9e7010bb7ce4e587e654ef9c1ee22e44db4b5c4 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/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" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid -Copt-level=3" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 842cd4c03aa415172e9279941845603e2bc5533d59cdbe8237d68fcd069a367e [INFO] running `Command { std: "docker" "start" "-a" "842cd4c03aa415172e9279941845603e2bc5533d59cdbe8237d68fcd069a367e", kill_on_drop: false }` [INFO] [stderr] Compiling yansi v1.0.1 [INFO] [stderr] Compiling futures-core v0.3.31 [INFO] [stderr] Compiling tracing-core v0.1.34 [INFO] [stderr] Compiling futures-sink v0.3.31 [INFO] [stderr] Compiling futures-task v0.3.31 [INFO] [stderr] Compiling tokio v1.48.0 [INFO] [stderr] Compiling futures-io v0.3.31 [INFO] [stderr] Compiling indexmap v2.11.4 [INFO] [stderr] Compiling log v0.4.28 [INFO] [stderr] Compiling rocket v0.5.1 (/opt/rustwide/workdir) [INFO] [stderr] Compiling futures-channel v0.3.31 [INFO] [stderr] Compiling futures-util v0.3.31 [INFO] [stderr] Compiling proc-macro2-diagnostics v0.10.1 [INFO] [stderr] Compiling tracing v0.1.41 [INFO] [stderr] Compiling devise_core v0.4.2 [INFO] [stderr] Compiling pear_codegen v0.2.9 [INFO] [stderr] Compiling futures v0.3.31 [INFO] [stderr] Compiling pear v0.2.9 [INFO] [stderr] Compiling hyper v0.14.32 [INFO] [stderr] Compiling figment v0.10.19 [INFO] [stderr] Compiling rocket_http v0.5.1 [INFO] [stderr] Compiling tokio-util v0.7.16 [INFO] [stderr] Compiling tokio-stream v0.1.17 [INFO] [stderr] Compiling devise_codegen v0.4.2 [INFO] [stderr] Compiling h2 v0.3.27 [INFO] [stderr] Compiling multer v3.1.0 [INFO] [stderr] Compiling devise v0.4.2 [INFO] [stderr] Compiling rocket_codegen v0.5.1 [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/lib.rs:6:13 [INFO] [stdout] | [INFO] [stdout] 6 | #![cfg_attr(nightly, feature(doc_cfg))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/lib.rs:7:13 [INFO] [stdout] | [INFO] [stdout] 7 | #![cfg_attr(nightly, feature(decl_macro))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/outcome.rs:630:1 [INFO] [stdout] | [INFO] [stdout] 630 | / crate::export! { [INFO] [stdout] 631 | | /// Unwraps a [`Success`](Outcome::Success) or propagates a `Forward` or [INFO] [stdout] 632 | | /// `Error` by returning early. [INFO] [stdout] 633 | | /// [INFO] [stdout] ... | [INFO] [stdout] 711 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/request/mod.rs:19:1 [INFO] [stdout] | [INFO] [stdout] 19 | / crate::export! { [INFO] [stdout] 20 | | /// Store and immediately retrieve a vector-like value `$v` (`String` or [INFO] [stdout] 21 | | /// `Vec`) in `$request`'s local cache using a locally generated [INFO] [stdout] 22 | | /// anonymous type to avoid type conflicts. [INFO] [stdout] ... | [INFO] [stdout] 67 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/request/mod.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | / crate::export! { [INFO] [stdout] 70 | | /// Store and immediately retrieve a value `$v` in `$request`'s local cache [INFO] [stdout] 71 | | /// using a locally generated anonymous type to avoid type conflicts. [INFO] [stdout] 72 | | /// [INFO] [stdout] ... | [INFO] [stdout] 113 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/mod.rs:206:1 [INFO] [stdout] | [INFO] [stdout] 206 | / crate::export! { [INFO] [stdout] 207 | | /// Retrofitted support for [`Stream`]s with `yield`, `for await` syntax. [INFO] [stdout] 208 | | /// [INFO] [stdout] 209 | | /// [`Stream`]: https://docs.rs/futures/0.3/futures/stream/trait.Stream.html [INFO] [stdout] ... | [INFO] [stdout] 288 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/reader.rs:196:1 [INFO] [stdout] | [INFO] [stdout] 196 | / crate::export! { [INFO] [stdout] 197 | | /// Type and stream expression macro for [`struct@ReaderStream`]. [INFO] [stdout] 198 | | /// [INFO] [stdout] 199 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 207 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/bytes.rs:75:1 [INFO] [stdout] | [INFO] [stdout] 75 | / crate::export! { [INFO] [stdout] 76 | | /// Type and stream expression macro for [`struct@ByteStream`]. [INFO] [stdout] 77 | | /// [INFO] [stdout] 78 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/text.rs:85:1 [INFO] [stdout] | [INFO] [stdout] 85 | / crate::export! { [INFO] [stdout] 86 | | /// Type and stream expression macro for [`struct@TextStream`]. [INFO] [stdout] 87 | | /// [INFO] [stdout] 88 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 96 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/sse.rs:588:1 [INFO] [stdout] | [INFO] [stdout] 588 | / crate::export! { [INFO] [stdout] 589 | | /// Type and stream expression macro for [`struct@EventStream`]. [INFO] [stdout] 590 | | /// [INFO] [stdout] 591 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 602 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/config.rs:105:16 [INFO] [stdout] | [INFO] [stdout] 105 | #[cfg_attr(nightly, doc(cfg(feature = "tls")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/config.rs:112:16 [INFO] [stdout] | [INFO] [stdout] 112 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/shutdown.rs:21:12 [INFO] [stdout] | [INFO] [stdout] 21 | #[cfg_attr(nightly, doc(cfg(unix)))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/shutdown.rs:218:16 [INFO] [stdout] | [INFO] [stdout] 218 | #[cfg_attr(nightly, doc(cfg(unix)))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/form/validate.rs:90:1 [INFO] [stdout] | [INFO] [stdout] 90 | / crate::export! { [INFO] [stdout] 91 | | /// A helper macro for custom validation error messages. [INFO] [stdout] 92 | | /// [INFO] [stdout] 93 | | /// The macro works similar to [`std::format!`]. It generates a form [INFO] [stdout] ... | [INFO] [stdout] 158 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/fs/server.rs:405:1 [INFO] [stdout] | [INFO] [stdout] 405 | / crate::export! { [INFO] [stdout] 406 | | /// Generates a crate-relative version of a path. [INFO] [stdout] 407 | | /// [INFO] [stdout] 408 | | /// This macro is primarily intended for use with [`FileServer`] to serve [INFO] [stdout] ... | [INFO] [stdout] 453 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `broken_fmt` [INFO] [stdout] --> src/server.rs:76:15 [INFO] [stdout] | [INFO] [stdout] 76 | #[cfg(not(broken_fmt))] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `broken_fmt` [INFO] [stdout] --> src/server.rs:165:19 [INFO] [stdout] | [INFO] [stdout] 165 | #[cfg(not(broken_fmt))] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: method `name` is never used [INFO] [stdout] --> src/shield/policy.rs:69:8 [INFO] [stdout] | [INFO] [stdout] 68 | pub(crate) trait SubPolicy: Send + Sync { [INFO] [stdout] | --------- method in this trait [INFO] [stdout] 69 | fn name(&self) -> &'static UncasedStr; [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `1` is never read [INFO] [stdout] --> src/cookies.rs:173:29 [INFO] [stdout] | [INFO] [stdout] 173 | Remove(Cookie<'static>, bool), [INFO] [stdout] | ------ ^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `Op` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis [INFO] [stdout] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field [INFO] [stdout] | [INFO] [stdout] 173 - Remove(Cookie<'static>, bool), [INFO] [stdout] 173 + Remove(Cookie<'static>, ()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/outcome.rs:737:9 [INFO] [stdout] | [INFO] [stdout] 736 | pub(crate) fn log_display(&self) -> Display<'_, 'r> { [INFO] [stdout] | --------------------------------------------------- move the `impl` block outside of this method `log_display` [INFO] [stdout] 737 | impl fmt::Display for Display<'_, '_> { [INFO] [stdout] | ^^^^^------------^^^^^-------^^^^^^^^ [INFO] [stdout] | | | [INFO] [stdout] | | `Display` is not local [INFO] [stdout] | `Display` is not local [INFO] [stdout] | [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/form/context.rs:223:33 [INFO] [stdout] | [INFO] [stdout] 223 | pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 223 - pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] 223 + pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/form/context.rs:272:39 [INFO] [stdout] | [INFO] [stdout] 272 | pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 272 - pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] 272 + pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 2m 13s [INFO] running `Command { std: "docker" "inspect" "842cd4c03aa415172e9279941845603e2bc5533d59cdbe8237d68fcd069a367e", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "842cd4c03aa415172e9279941845603e2bc5533d59cdbe8237d68fcd069a367e", kill_on_drop: false }` [INFO] [stdout] 842cd4c03aa415172e9279941845603e2bc5533d59cdbe8237d68fcd069a367e [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/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" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid -Copt-level=3" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] f1a536e0f810023b906c2bf08bc5b6dabdc4ac97bee338b271a94eaafa4df9d6 [INFO] running `Command { std: "docker" "start" "-a" "f1a536e0f810023b906c2bf08bc5b6dabdc4ac97bee338b271a94eaafa4df9d6", kill_on_drop: false }` [INFO] [stderr] Compiling figment v0.10.19 [INFO] [stderr] Compiling diff v0.1.13 [INFO] [stderr] Compiling pretty_assertions v1.4.1 [INFO] [stderr] Compiling rocket v0.5.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/lib.rs:6:13 [INFO] [stdout] | [INFO] [stdout] 6 | #![cfg_attr(nightly, feature(doc_cfg))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/lib.rs:7:13 [INFO] [stdout] | [INFO] [stdout] 7 | #![cfg_attr(nightly, feature(decl_macro))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/outcome.rs:630:1 [INFO] [stdout] | [INFO] [stdout] 630 | / crate::export! { [INFO] [stdout] 631 | | /// Unwraps a [`Success`](Outcome::Success) or propagates a `Forward` or [INFO] [stdout] 632 | | /// `Error` by returning early. [INFO] [stdout] 633 | | /// [INFO] [stdout] ... | [INFO] [stdout] 711 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/request/mod.rs:19:1 [INFO] [stdout] | [INFO] [stdout] 19 | / crate::export! { [INFO] [stdout] 20 | | /// Store and immediately retrieve a vector-like value `$v` (`String` or [INFO] [stdout] 21 | | /// `Vec`) in `$request`'s local cache using a locally generated [INFO] [stdout] 22 | | /// anonymous type to avoid type conflicts. [INFO] [stdout] ... | [INFO] [stdout] 67 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/request/mod.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | / crate::export! { [INFO] [stdout] 70 | | /// Store and immediately retrieve a value `$v` in `$request`'s local cache [INFO] [stdout] 71 | | /// using a locally generated anonymous type to avoid type conflicts. [INFO] [stdout] 72 | | /// [INFO] [stdout] ... | [INFO] [stdout] 113 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/mod.rs:206:1 [INFO] [stdout] | [INFO] [stdout] 206 | / crate::export! { [INFO] [stdout] 207 | | /// Retrofitted support for [`Stream`]s with `yield`, `for await` syntax. [INFO] [stdout] 208 | | /// [INFO] [stdout] 209 | | /// [`Stream`]: https://docs.rs/futures/0.3/futures/stream/trait.Stream.html [INFO] [stdout] ... | [INFO] [stdout] 288 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/reader.rs:196:1 [INFO] [stdout] | [INFO] [stdout] 196 | / crate::export! { [INFO] [stdout] 197 | | /// Type and stream expression macro for [`struct@ReaderStream`]. [INFO] [stdout] 198 | | /// [INFO] [stdout] 199 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 207 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/bytes.rs:75:1 [INFO] [stdout] | [INFO] [stdout] 75 | / crate::export! { [INFO] [stdout] 76 | | /// Type and stream expression macro for [`struct@ByteStream`]. [INFO] [stdout] 77 | | /// [INFO] [stdout] 78 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/text.rs:85:1 [INFO] [stdout] | [INFO] [stdout] 85 | / crate::export! { [INFO] [stdout] 86 | | /// Type and stream expression macro for [`struct@TextStream`]. [INFO] [stdout] 87 | | /// [INFO] [stdout] 88 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 96 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/sse.rs:588:1 [INFO] [stdout] | [INFO] [stdout] 588 | / crate::export! { [INFO] [stdout] 589 | | /// Type and stream expression macro for [`struct@EventStream`]. [INFO] [stdout] 590 | | /// [INFO] [stdout] 591 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 602 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/config.rs:105:16 [INFO] [stdout] | [INFO] [stdout] 105 | #[cfg_attr(nightly, doc(cfg(feature = "tls")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/config.rs:112:16 [INFO] [stdout] | [INFO] [stdout] 112 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/shutdown.rs:21:12 [INFO] [stdout] | [INFO] [stdout] 21 | #[cfg_attr(nightly, doc(cfg(unix)))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/shutdown.rs:218:16 [INFO] [stdout] | [INFO] [stdout] 218 | #[cfg_attr(nightly, doc(cfg(unix)))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/form/validate.rs:90:1 [INFO] [stdout] | [INFO] [stdout] 90 | / crate::export! { [INFO] [stdout] 91 | | /// A helper macro for custom validation error messages. [INFO] [stdout] 92 | | /// [INFO] [stdout] 93 | | /// The macro works similar to [`std::format!`]. It generates a form [INFO] [stdout] ... | [INFO] [stdout] 158 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/fs/server.rs:405:1 [INFO] [stdout] | [INFO] [stdout] 405 | / crate::export! { [INFO] [stdout] 406 | | /// Generates a crate-relative version of a path. [INFO] [stdout] 407 | | /// [INFO] [stdout] 408 | | /// This macro is primarily intended for use with [`FileServer`] to serve [INFO] [stdout] ... | [INFO] [stdout] 453 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `broken_fmt` [INFO] [stdout] --> src/server.rs:76:15 [INFO] [stdout] | [INFO] [stdout] 76 | #[cfg(not(broken_fmt))] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `broken_fmt` [INFO] [stdout] --> src/server.rs:165:19 [INFO] [stdout] | [INFO] [stdout] 165 | #[cfg(not(broken_fmt))] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/lib.rs:6:13 [INFO] [stdout] | [INFO] [stdout] 6 | #![cfg_attr(nightly, feature(doc_cfg))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/lib.rs:7:13 [INFO] [stdout] | [INFO] [stdout] 7 | #![cfg_attr(nightly, feature(decl_macro))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/outcome.rs:630:1 [INFO] [stdout] | [INFO] [stdout] 630 | / crate::export! { [INFO] [stdout] 631 | | /// Unwraps a [`Success`](Outcome::Success) or propagates a `Forward` or [INFO] [stdout] 632 | | /// `Error` by returning early. [INFO] [stdout] 633 | | /// [INFO] [stdout] ... | [INFO] [stdout] 711 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/request/mod.rs:19:1 [INFO] [stdout] | [INFO] [stdout] 19 | / crate::export! { [INFO] [stdout] 20 | | /// Store and immediately retrieve a vector-like value `$v` (`String` or [INFO] [stdout] 21 | | /// `Vec`) in `$request`'s local cache using a locally generated [INFO] [stdout] 22 | | /// anonymous type to avoid type conflicts. [INFO] [stdout] ... | [INFO] [stdout] 67 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/request/mod.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | / crate::export! { [INFO] [stdout] 70 | | /// Store and immediately retrieve a value `$v` in `$request`'s local cache [INFO] [stdout] 71 | | /// using a locally generated anonymous type to avoid type conflicts. [INFO] [stdout] 72 | | /// [INFO] [stdout] ... | [INFO] [stdout] 113 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/mod.rs:206:1 [INFO] [stdout] | [INFO] [stdout] 206 | / crate::export! { [INFO] [stdout] 207 | | /// Retrofitted support for [`Stream`]s with `yield`, `for await` syntax. [INFO] [stdout] 208 | | /// [INFO] [stdout] 209 | | /// [`Stream`]: https://docs.rs/futures/0.3/futures/stream/trait.Stream.html [INFO] [stdout] ... | [INFO] [stdout] 288 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/reader.rs:196:1 [INFO] [stdout] | [INFO] [stdout] 196 | / crate::export! { [INFO] [stdout] 197 | | /// Type and stream expression macro for [`struct@ReaderStream`]. [INFO] [stdout] 198 | | /// [INFO] [stdout] 199 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 207 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/bytes.rs:75:1 [INFO] [stdout] | [INFO] [stdout] 75 | / crate::export! { [INFO] [stdout] 76 | | /// Type and stream expression macro for [`struct@ByteStream`]. [INFO] [stdout] 77 | | /// [INFO] [stdout] 78 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/text.rs:85:1 [INFO] [stdout] | [INFO] [stdout] 85 | / crate::export! { [INFO] [stdout] 86 | | /// Type and stream expression macro for [`struct@TextStream`]. [INFO] [stdout] 87 | | /// [INFO] [stdout] 88 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 96 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/response/stream/sse.rs:588:1 [INFO] [stdout] | [INFO] [stdout] 588 | / crate::export! { [INFO] [stdout] 589 | | /// Type and stream expression macro for [`struct@EventStream`]. [INFO] [stdout] 590 | | /// [INFO] [stdout] 591 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 602 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/config.rs:105:16 [INFO] [stdout] | [INFO] [stdout] 105 | #[cfg_attr(nightly, doc(cfg(feature = "tls")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/config.rs:112:16 [INFO] [stdout] | [INFO] [stdout] 112 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/shutdown.rs:21:12 [INFO] [stdout] | [INFO] [stdout] 21 | #[cfg_attr(nightly, doc(cfg(unix)))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/config/shutdown.rs:218:16 [INFO] [stdout] | [INFO] [stdout] 218 | #[cfg_attr(nightly, doc(cfg(unix)))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/form/validate.rs:90:1 [INFO] [stdout] | [INFO] [stdout] 90 | / crate::export! { [INFO] [stdout] 91 | | /// A helper macro for custom validation error messages. [INFO] [stdout] 92 | | /// [INFO] [stdout] 93 | | /// The macro works similar to [`std::format!`]. It generates a form [INFO] [stdout] ... | [INFO] [stdout] 158 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> src/fs/server.rs:405:1 [INFO] [stdout] | [INFO] [stdout] 405 | / crate::export! { [INFO] [stdout] 406 | | /// Generates a crate-relative version of a path. [INFO] [stdout] 407 | | /// [INFO] [stdout] 408 | | /// This macro is primarily intended for use with [`FileServer`] to serve [INFO] [stdout] ... | [INFO] [stdout] 453 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `crate::export` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `broken_fmt` [INFO] [stdout] --> src/server.rs:76:15 [INFO] [stdout] | [INFO] [stdout] 76 | #[cfg(not(broken_fmt))] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `broken_fmt` [INFO] [stdout] --> src/server.rs:165:19 [INFO] [stdout] | [INFO] [stdout] 165 | #[cfg(not(broken_fmt))] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: method `name` is never used [INFO] [stdout] --> src/shield/policy.rs:69:8 [INFO] [stdout] | [INFO] [stdout] 68 | pub(crate) trait SubPolicy: Send + Sync { [INFO] [stdout] | --------- method in this trait [INFO] [stdout] 69 | fn name(&self) -> &'static UncasedStr; [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `1` is never read [INFO] [stdout] --> src/cookies.rs:173:29 [INFO] [stdout] | [INFO] [stdout] 173 | Remove(Cookie<'static>, bool), [INFO] [stdout] | ------ ^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `Op` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis [INFO] [stdout] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field [INFO] [stdout] | [INFO] [stdout] 173 - Remove(Cookie<'static>, bool), [INFO] [stdout] 173 + Remove(Cookie<'static>, ()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/outcome.rs:737:9 [INFO] [stdout] | [INFO] [stdout] 736 | pub(crate) fn log_display(&self) -> Display<'_, 'r> { [INFO] [stdout] | --------------------------------------------------- move the `impl` block outside of this method `log_display` [INFO] [stdout] 737 | impl fmt::Display for Display<'_, '_> { [INFO] [stdout] | ^^^^^------------^^^^^-------^^^^^^^^ [INFO] [stdout] | | | [INFO] [stdout] | | `Display` is not local [INFO] [stdout] | `Display` is not local [INFO] [stdout] | [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/form/context.rs:223:33 [INFO] [stdout] | [INFO] [stdout] 223 | pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 223 - pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] 223 + pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/form/context.rs:272:39 [INFO] [stdout] | [INFO] [stdout] 272 | pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 272 - pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] 272 + pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: method `name` is never used [INFO] [stdout] --> src/shield/policy.rs:69:8 [INFO] [stdout] | [INFO] [stdout] 68 | pub(crate) trait SubPolicy: Send + Sync { [INFO] [stdout] | --------- method in this trait [INFO] [stdout] 69 | fn name(&self) -> &'static UncasedStr; [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `1` is never read [INFO] [stdout] --> src/cookies.rs:173:29 [INFO] [stdout] | [INFO] [stdout] 173 | Remove(Cookie<'static>, bool), [INFO] [stdout] | ------ ^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `Op` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis [INFO] [stdout] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field [INFO] [stdout] | [INFO] [stdout] 173 - Remove(Cookie<'static>, bool), [INFO] [stdout] 173 + Remove(Cookie<'static>, ()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/outcome.rs:737:9 [INFO] [stdout] | [INFO] [stdout] 736 | pub(crate) fn log_display(&self) -> Display<'_, 'r> { [INFO] [stdout] | --------------------------------------------------- move the `impl` block outside of this method `log_display` [INFO] [stdout] 737 | impl fmt::Display for Display<'_, '_> { [INFO] [stdout] | ^^^^^------------^^^^^-------^^^^^^^^ [INFO] [stdout] | | | [INFO] [stdout] | | `Display` is not local [INFO] [stdout] | `Display` is not local [INFO] [stdout] | [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/form/context.rs:223:33 [INFO] [stdout] | [INFO] [stdout] 223 | pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 223 - pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] 223 + pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/form/context.rs:272:39 [INFO] [stdout] | [INFO] [stdout] 272 | pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 272 - pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] 272 + pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: missing documentation for a function [INFO] [stdout] --> src/catcher/handler.rs:122:1 [INFO] [stdout] | [INFO] [stdout] 122 | pub fn dummy_handler<'r>(_: Status, _: &'r Request<'_>) -> BoxFuture<'r> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] note: the lint level is defined here [INFO] [stdout] --> src/lib.rs:10:9 [INFO] [stdout] | [INFO] [stdout] 10 | #![warn(missing_docs)] [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module [INFO] [stdout] --> tests/shutdown-fairings.rs:129:5 [INFO] [stdout] | [INFO] [stdout] 129 | #[get("/")] [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `background_tasks_dont_prevent_terminate` [INFO] [stdout] = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute [INFO] [stdout] = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stdout] = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module [INFO] [stdout] --> tests/file_server.rs:122:5 [INFO] [stdout] | [INFO] [stdout] 122 | #[get("/", rank = 20)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `test_forwarding` [INFO] [stdout] = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute [INFO] [stdout] = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stdout] = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module [INFO] [stdout] --> tests/file_server.rs:125:5 [INFO] [stdout] | [INFO] [stdout] 125 | #[get("//", rank = 20)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `test_forwarding` [INFO] [stdout] = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute [INFO] [stdout] = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `rocket` (lib test); 24 warnings emitted [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `/opt/rustwide/rustup-home/toolchains/d98a5da813da67eb189387b8ccfb73cf481275d8/bin/rustc --crate-name rocket --edition=2021 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --test --cfg 'feature="default"' --cfg 'feature="http2"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "http2", "json", "msgpack", "mtls", "rmp-serde", "secrets", "serde_json", "tls", "uuid", "uuid_"))' -C metadata=070adbe22d6ec666 -C extra-filename=-da2cce737980abf2 --out-dir /opt/rustwide/target/debug/deps -L dependency=/opt/rustwide/target/debug/deps --extern async_stream=/opt/rustwide/target/debug/deps/libasync_stream-9268958ca0c690c7.rlib --extern async_trait=/opt/rustwide/target/debug/deps/libasync_trait-6a94b5bc6ceef2c9.so --extern atomic=/opt/rustwide/target/debug/deps/libatomic-e4251e7669031793.rlib --extern binascii=/opt/rustwide/target/debug/deps/libbinascii-16bd6da115a6815f.rlib --extern bytes=/opt/rustwide/target/debug/deps/libbytes-ac1de41d75287ad9.rlib --extern either=/opt/rustwide/target/debug/deps/libeither-0ca5e99180d48806.rlib --extern figment=/opt/rustwide/target/debug/deps/libfigment-98c480ea1f0365b2.rlib --extern futures=/opt/rustwide/target/debug/deps/libfutures-6ab4b7ed40757df0.rlib --extern indexmap=/opt/rustwide/target/debug/deps/libindexmap-5ba2ba3408c7bf78.rlib --extern log=/opt/rustwide/target/debug/deps/liblog-660afbac4a15879a.rlib --extern memchr=/opt/rustwide/target/debug/deps/libmemchr-38bf064dbe8703ff.rlib --extern multer=/opt/rustwide/target/debug/deps/libmulter-00ff45c4505fc0d5.rlib --extern num_cpus=/opt/rustwide/target/debug/deps/libnum_cpus-e4412cc24bcad615.rlib --extern parking_lot=/opt/rustwide/target/debug/deps/libparking_lot-3aac33fcb2cb613b.rlib --extern pin_project_lite=/opt/rustwide/target/debug/deps/libpin_project_lite-669ab13378d6d882.rlib --extern pretty_assertions=/opt/rustwide/target/debug/deps/libpretty_assertions-c212e6dc3e630512.rlib --extern rand=/opt/rustwide/target/debug/deps/librand-0da403c9e2581ad1.rlib --extern ref_cast=/opt/rustwide/target/debug/deps/libref_cast-2aec7bf489bdf210.rlib --extern rocket_codegen=/opt/rustwide/target/debug/deps/librocket_codegen-a711f9daad3ef3d8.so --extern rocket_http=/opt/rustwide/target/debug/deps/librocket_http-c189d735a7e107df.rlib --extern serde=/opt/rustwide/target/debug/deps/libserde-8c76e9bf999385e7.rlib --extern state=/opt/rustwide/target/debug/deps/libstate-56739062142ee90e.rlib --extern tempfile=/opt/rustwide/target/debug/deps/libtempfile-6ec37aa4cec1d701.rlib --extern time=/opt/rustwide/target/debug/deps/libtime-dc4c14ec591cda27.rlib --extern tokio=/opt/rustwide/target/debug/deps/libtokio-660fc30fc5d0ed8e.rlib --extern tokio_stream=/opt/rustwide/target/debug/deps/libtokio_stream-2ff8793a731a041d.rlib --extern tokio_util=/opt/rustwide/target/debug/deps/libtokio_util-6a79513d54ab3f2e.rlib --extern ubyte=/opt/rustwide/target/debug/deps/libubyte-63c45788ec3045d1.rlib --extern yansi=/opt/rustwide/target/debug/deps/libyansi-fae9658265e2622b.rlib --cap-lints=forbid -Copt-level=3 --cfg nightly` (signal: 9, SIGKILL: kill) [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] running `Command { std: "docker" "inspect" "f1a536e0f810023b906c2bf08bc5b6dabdc4ac97bee338b271a94eaafa4df9d6", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "f1a536e0f810023b906c2bf08bc5b6dabdc4ac97bee338b271a94eaafa4df9d6", kill_on_drop: false }` [INFO] [stdout] f1a536e0f810023b906c2bf08bc5b6dabdc4ac97bee338b271a94eaafa4df9d6