[INFO] fetching crate marker_api 0.5.0...
[INFO] testing marker_api-0.5.0 against master#733b47ea4b1b86216f14ef56e49440c33933f230+rustflags=-Copt-level=3 for pr-138759
[INFO] extracting crate marker_api 0.5.0 into /workspace/builds/worker-2-tc2/source
[INFO] started tweaking crates.io crate marker_api 0.5.0
[INFO] finished tweaking crates.io crate marker_api 0.5.0
[INFO] tweaked toml for crates.io crate marker_api 0.5.0 written to /workspace/builds/worker-2-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate marker_api 0.5.0 on toolchain 733b47ea4b1b86216f14ef56e49440c33933f230
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+733b47ea4b1b86216f14ef56e49440c33933f230" "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" "+733b47ea4b1b86216f14ef56e49440c33933f230" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 10 packages to latest compatible versions
[INFO] [stderr]       Adding typed-builder v0.18.2 (available: v0.22.0)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+733b47ea4b1b86216f14ef56e49440c33933f230" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/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" "+733b47ea4b1b86216f14ef56e49440c33933f230" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 8c387d6544b41bc34cfd5082065869a3836746381a4cda6764a8ca9ebc0a4ceb
[INFO] running `Command { std: "docker" "start" "-a" "8c387d6544b41bc34cfd5082065869a3836746381a4cda6764a8ca9ebc0a4ceb", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "8c387d6544b41bc34cfd5082065869a3836746381a4cda6764a8ca9ebc0a4ceb", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "8c387d6544b41bc34cfd5082065869a3836746381a4cda6764a8ca9ebc0a4ceb", kill_on_drop: false }`
[INFO] [stdout] 8c387d6544b41bc34cfd5082065869a3836746381a4cda6764a8ca9ebc0a4ceb
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/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" "+733b47ea4b1b86216f14ef56e49440c33933f230" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 59a98bda830976632f02f614c79b5ba1dbbbad3c89280596577e143101513945
[INFO] running `Command { std: "docker" "start" "-a" "59a98bda830976632f02f614c79b5ba1dbbbad3c89280596577e143101513945", kill_on_drop: false }`
[INFO] [stderr]    Compiling marker_api v0.5.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `marker`
[INFO] [stdout]   --> src/lib.rs:10:13
[INFO] [stdout]    |
[INFO] [stdout] 10 | #![cfg_attr(marker, warn(marker::marker_lints::not_using_has_span_trait))]
[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(marker)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(marker)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/fn_ty.rs:31:1
[INFO] [stdout]     |
[INFO] [stdout] 31  | super::impl_ty_data!(FnTy<'ast>, Fn);
[INFO] [stdout]     | ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/fn_ty.rs:62:1
[INFO] [stdout]     |
[INFO] [stdout] 62  | super::impl_ty_data!(ClosureTy<'ast>, Closure);
[INFO] [stdout]     | ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/other_ty.rs:12:1
[INFO] [stdout]     |
[INFO] [stdout] 12  | super::impl_ty_data!(UnstableTy<'ast>, Unstable);
[INFO] [stdout]     | ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:19:1
[INFO] [stdout]     |
[INFO] [stdout] 19  | super::impl_ty_data!(BoolTy<'ast>, Bool);
[INFO] [stdout]     | ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:52:1
[INFO] [stdout]     |
[INFO] [stdout] 52  | super::impl_ty_data!(NumTy<'ast>, Num);
[INFO] [stdout]     | -------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:82:1
[INFO] [stdout]     |
[INFO] [stdout] 82  | super::impl_ty_data!(TextTy<'ast>, Text);
[INFO] [stdout]     | ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:97:1
[INFO] [stdout]     |
[INFO] [stdout] 97  | super::impl_ty_data!(NeverTy<'ast>, Never);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/ptr_ty.rs:35:1
[INFO] [stdout]     |
[INFO] [stdout] 35  | super::impl_ty_data!(RefTy<'ast>, Ref);
[INFO] [stdout]     | -------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/ptr_ty.rs:58:1
[INFO] [stdout]     |
[INFO] [stdout] 58  | super::impl_ty_data!(RawPtrTy<'ast>, RawPtr);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/ptr_ty.rs:91:1
[INFO] [stdout]     |
[INFO] [stdout] 91  | super::impl_ty_data!(FnPtrTy<'ast>, FnPtr);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/sequence_ty.rs:21:1
[INFO] [stdout]     |
[INFO] [stdout] 21  | super::impl_ty_data!(TupleTy<'ast>, Tuple);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/sequence_ty.rs:49:1
[INFO] [stdout]     |
[INFO] [stdout] 49  | super::impl_ty_data!(SliceTy<'ast>, Slice);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/sequence_ty.rs:77:1
[INFO] [stdout]     |
[INFO] [stdout] 77  | super::impl_ty_data!(ArrayTy<'ast>, Array);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/trait_ty.rs:23:1
[INFO] [stdout]     |
[INFO] [stdout] 23  | super::impl_ty_data!(TraitObjTy<'ast>, TraitObj);
[INFO] [stdout]     | ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/user_ty.rs:35:1
[INFO] [stdout]     |
[INFO] [stdout] 35  | super::impl_ty_data!(AdtTy<'ast>, Adt);
[INFO] [stdout]     | -------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/user_ty.rs:62:1
[INFO] [stdout]     |
[INFO] [stdout] 62  | super::impl_ty_data!(GenericTy<'ast>, Generic);
[INFO] [stdout]     | ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/user_ty.rs:84:1
[INFO] [stdout]     |
[INFO] [stdout] 84  | super::impl_ty_data!(AliasTy<'ast>, Alias);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/ast/expr/control_flow_expr.rs:475:22
[INFO] [stdout]     |
[INFO] [stdout] 475 |     pub fn condition(&self) -> ExprKind {
[INFO] [stdout]     |                      ^^^^^     -------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                      |
[INFO] [stdout]     |                      this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 475 |     pub fn condition(&self) -> ExprKind<'_> {
[INFO] [stdout]     |                                        ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/ast/expr/control_flow_expr.rs:536:21
[INFO] [stdout]     |
[INFO] [stdout] 536 |     pub fn iterable(&self) -> ExprKind {
[INFO] [stdout]     |                     ^^^^^     -------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 536 |     pub fn iterable(&self) -> ExprKind<'_> {
[INFO] [stdout]     |                                       ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]   --> src/ast/item/ty_alias_item.rs:42:23
[INFO] [stdout]    |
[INFO] [stdout] 42 |     pub fn aliased_ty(&self) -> Option<TyKind> {
[INFO] [stdout]    |                       ^^^^^            ------ the lifetime gets resolved as `'_`
[INFO] [stdout]    |                       |
[INFO] [stdout]    |                       this lifetime flows to the output
[INFO] [stdout]    |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]    |
[INFO] [stdout] 42 |     pub fn aliased_ty(&self) -> Option<TyKind<'_>> {
[INFO] [stdout]    |                                              ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]   --> src/ast/item/impl_item.rs:72:15
[INFO] [stdout]    |
[INFO] [stdout] 72 |     pub fn ty(&self) -> TyKind {
[INFO] [stdout]    |               ^^^^^     ------ the lifetime gets resolved as `'_`
[INFO] [stdout]    |               |
[INFO] [stdout]    |               this lifetime flows to the output
[INFO] [stdout]    |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]    |
[INFO] [stdout] 72 |     pub fn ty(&self) -> TyKind<'_> {
[INFO] [stdout]    |                               ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/ast/stmt.rs:129:16
[INFO] [stdout]     |
[INFO] [stdout] 129 |     pub fn els(&self) -> Option<ExprKind> {
[INFO] [stdout]     |                ^^^^^            -------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                |
[INFO] [stdout]     |                this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 129 |     pub fn els(&self) -> Option<ExprKind<'_>> {
[INFO] [stdout]     |                                         ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/span.rs:441:28
[INFO] [stdout]     |
[INFO] [stdout] 441 |     pub fn try_to_file_pos(&self, span_pos: SpanPos) -> Option<FilePos> {
[INFO] [stdout]     |                            ^^^^^                               ------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                            |
[INFO] [stdout]     |                            this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 441 |     pub fn try_to_file_pos(&self, span_pos: SpanPos) -> Option<FilePos<'_>> {
[INFO] [stdout]     |                                                                       ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/span.rs:447:24
[INFO] [stdout]     |
[INFO] [stdout] 447 |     pub fn to_file_pos(&self, span_pos: SpanPos) -> FilePos {
[INFO] [stdout]     |                        ^^^^^                        ------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 447 |     pub fn to_file_pos(&self, span_pos: SpanPos) -> FilePos<'_> {
[INFO] [stdout]     |                                                            ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 3.77s
[INFO] running `Command { std: "docker" "inspect" "59a98bda830976632f02f614c79b5ba1dbbbad3c89280596577e143101513945", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "59a98bda830976632f02f614c79b5ba1dbbbad3c89280596577e143101513945", kill_on_drop: false }`
[INFO] [stdout] 59a98bda830976632f02f614c79b5ba1dbbbad3c89280596577e143101513945
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/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" "+733b47ea4b1b86216f14ef56e49440c33933f230" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] a2917d2171549b6ba2f0a7af2e1d95e5537ab7f4cfab0614eb57f669e3c07b84
[INFO] running `Command { std: "docker" "start" "-a" "a2917d2171549b6ba2f0a7af2e1d95e5537ab7f4cfab0614eb57f669e3c07b84", kill_on_drop: false }`
[INFO] [stderr]    Compiling dissimilar v1.0.10
[INFO] [stdout] warning: unexpected `cfg` condition name: `marker`
[INFO] [stdout]   --> src/lib.rs:10:13
[INFO] [stdout]    |
[INFO] [stdout] 10 | #![cfg_attr(marker, warn(marker::marker_lints::not_using_has_span_trait))]
[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(marker)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(marker)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/fn_ty.rs:31:1
[INFO] [stdout]     |
[INFO] [stdout] 31  | super::impl_ty_data!(FnTy<'ast>, Fn);
[INFO] [stdout]     | ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/fn_ty.rs:62:1
[INFO] [stdout]     |
[INFO] [stdout] 62  | super::impl_ty_data!(ClosureTy<'ast>, Closure);
[INFO] [stdout]     | ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/other_ty.rs:12:1
[INFO] [stdout]     |
[INFO] [stdout] 12  | super::impl_ty_data!(UnstableTy<'ast>, Unstable);
[INFO] [stdout]     | ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:19:1
[INFO] [stdout]     |
[INFO] [stdout] 19  | super::impl_ty_data!(BoolTy<'ast>, Bool);
[INFO] [stdout]     | ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:52:1
[INFO] [stdout]     |
[INFO] [stdout] 52  | super::impl_ty_data!(NumTy<'ast>, Num);
[INFO] [stdout]     | -------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:82:1
[INFO] [stdout]     |
[INFO] [stdout] 82  | super::impl_ty_data!(TextTy<'ast>, Text);
[INFO] [stdout]     | ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:97:1
[INFO] [stdout]     |
[INFO] [stdout] 97  | super::impl_ty_data!(NeverTy<'ast>, Never);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/ptr_ty.rs:35:1
[INFO] [stdout]     |
[INFO] [stdout] 35  | super::impl_ty_data!(RefTy<'ast>, Ref);
[INFO] [stdout]     | -------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/ptr_ty.rs:58:1
[INFO] [stdout]     |
[INFO] [stdout] 58  | super::impl_ty_data!(RawPtrTy<'ast>, RawPtr);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/ptr_ty.rs:91:1
[INFO] [stdout]     |
[INFO] [stdout] 91  | super::impl_ty_data!(FnPtrTy<'ast>, FnPtr);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/sequence_ty.rs:21:1
[INFO] [stdout]     |
[INFO] [stdout] 21  | super::impl_ty_data!(TupleTy<'ast>, Tuple);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/sequence_ty.rs:49:1
[INFO] [stdout]     |
[INFO] [stdout] 49  | super::impl_ty_data!(SliceTy<'ast>, Slice);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/sequence_ty.rs:77:1
[INFO] [stdout]     |
[INFO] [stdout] 77  | super::impl_ty_data!(ArrayTy<'ast>, Array);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/trait_ty.rs:23:1
[INFO] [stdout]     |
[INFO] [stdout] 23  | super::impl_ty_data!(TraitObjTy<'ast>, TraitObj);
[INFO] [stdout]     | ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/user_ty.rs:35:1
[INFO] [stdout]     |
[INFO] [stdout] 35  | super::impl_ty_data!(AdtTy<'ast>, Adt);
[INFO] [stdout]     | -------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/user_ty.rs:62:1
[INFO] [stdout]     |
[INFO] [stdout] 62  | super::impl_ty_data!(GenericTy<'ast>, Generic);
[INFO] [stdout]     | ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/user_ty.rs:84:1
[INFO] [stdout]     |
[INFO] [stdout] 84  | super::impl_ty_data!(AliasTy<'ast>, Alias);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/ast/expr/control_flow_expr.rs:475:22
[INFO] [stdout]     |
[INFO] [stdout] 475 |     pub fn condition(&self) -> ExprKind {
[INFO] [stdout]     |                      ^^^^^     -------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                      |
[INFO] [stdout]     |                      this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 475 |     pub fn condition(&self) -> ExprKind<'_> {
[INFO] [stdout]     |                                        ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/ast/expr/control_flow_expr.rs:536:21
[INFO] [stdout]     |
[INFO] [stdout] 536 |     pub fn iterable(&self) -> ExprKind {
[INFO] [stdout]     |                     ^^^^^     -------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 536 |     pub fn iterable(&self) -> ExprKind<'_> {
[INFO] [stdout]     |                                       ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]   --> src/ast/item/ty_alias_item.rs:42:23
[INFO] [stdout]    |
[INFO] [stdout] 42 |     pub fn aliased_ty(&self) -> Option<TyKind> {
[INFO] [stdout]    |                       ^^^^^            ------ the lifetime gets resolved as `'_`
[INFO] [stdout]    |                       |
[INFO] [stdout]    |                       this lifetime flows to the output
[INFO] [stdout]    |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]    |
[INFO] [stdout] 42 |     pub fn aliased_ty(&self) -> Option<TyKind<'_>> {
[INFO] [stdout]    |                                              ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]   --> src/ast/item/impl_item.rs:72:15
[INFO] [stdout]    |
[INFO] [stdout] 72 |     pub fn ty(&self) -> TyKind {
[INFO] [stdout]    |               ^^^^^     ------ the lifetime gets resolved as `'_`
[INFO] [stdout]    |               |
[INFO] [stdout]    |               this lifetime flows to the output
[INFO] [stdout]    |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]    |
[INFO] [stdout] 72 |     pub fn ty(&self) -> TyKind<'_> {
[INFO] [stdout]    |                               ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/ast/stmt.rs:129:16
[INFO] [stdout]     |
[INFO] [stdout] 129 |     pub fn els(&self) -> Option<ExprKind> {
[INFO] [stdout]     |                ^^^^^            -------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                |
[INFO] [stdout]     |                this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 129 |     pub fn els(&self) -> Option<ExprKind<'_>> {
[INFO] [stdout]     |                                         ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/span.rs:441:28
[INFO] [stdout]     |
[INFO] [stdout] 441 |     pub fn try_to_file_pos(&self, span_pos: SpanPos) -> Option<FilePos> {
[INFO] [stdout]     |                            ^^^^^                               ------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                            |
[INFO] [stdout]     |                            this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 441 |     pub fn try_to_file_pos(&self, span_pos: SpanPos) -> Option<FilePos<'_>> {
[INFO] [stdout]     |                                                                       ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/span.rs:447:24
[INFO] [stdout]     |
[INFO] [stdout] 447 |     pub fn to_file_pos(&self, span_pos: SpanPos) -> FilePos {
[INFO] [stdout]     |                        ^^^^^                        ------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 447 |     pub fn to_file_pos(&self, span_pos: SpanPos) -> FilePos<'_> {
[INFO] [stdout]     |                                                            ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling expect-test v1.5.1
[INFO] [stderr]    Compiling marker_api v0.5.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `marker`
[INFO] [stdout]   --> src/lib.rs:10:13
[INFO] [stdout]    |
[INFO] [stdout] 10 | #![cfg_attr(marker, warn(marker::marker_lints::not_using_has_span_trait))]
[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(marker)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(marker)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/fn_ty.rs:31:1
[INFO] [stdout]     |
[INFO] [stdout] 31  | super::impl_ty_data!(FnTy<'ast>, Fn);
[INFO] [stdout]     | ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/fn_ty.rs:62:1
[INFO] [stdout]     |
[INFO] [stdout] 62  | super::impl_ty_data!(ClosureTy<'ast>, Closure);
[INFO] [stdout]     | ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/other_ty.rs:12:1
[INFO] [stdout]     |
[INFO] [stdout] 12  | super::impl_ty_data!(UnstableTy<'ast>, Unstable);
[INFO] [stdout]     | ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:19:1
[INFO] [stdout]     |
[INFO] [stdout] 19  | super::impl_ty_data!(BoolTy<'ast>, Bool);
[INFO] [stdout]     | ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:52:1
[INFO] [stdout]     |
[INFO] [stdout] 52  | super::impl_ty_data!(NumTy<'ast>, Num);
[INFO] [stdout]     | -------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:82:1
[INFO] [stdout]     |
[INFO] [stdout] 82  | super::impl_ty_data!(TextTy<'ast>, Text);
[INFO] [stdout]     | ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/prim_ty.rs:97:1
[INFO] [stdout]     |
[INFO] [stdout] 97  | super::impl_ty_data!(NeverTy<'ast>, Never);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/ptr_ty.rs:35:1
[INFO] [stdout]     |
[INFO] [stdout] 35  | super::impl_ty_data!(RefTy<'ast>, Ref);
[INFO] [stdout]     | -------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/ptr_ty.rs:58:1
[INFO] [stdout]     |
[INFO] [stdout] 58  | super::impl_ty_data!(RawPtrTy<'ast>, RawPtr);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/ptr_ty.rs:91:1
[INFO] [stdout]     |
[INFO] [stdout] 91  | super::impl_ty_data!(FnPtrTy<'ast>, FnPtr);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/sequence_ty.rs:21:1
[INFO] [stdout]     |
[INFO] [stdout] 21  | super::impl_ty_data!(TupleTy<'ast>, Tuple);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/sequence_ty.rs:49:1
[INFO] [stdout]     |
[INFO] [stdout] 49  | super::impl_ty_data!(SliceTy<'ast>, Slice);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/sequence_ty.rs:77:1
[INFO] [stdout]     |
[INFO] [stdout] 77  | super::impl_ty_data!(ArrayTy<'ast>, Array);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/trait_ty.rs:23:1
[INFO] [stdout]     |
[INFO] [stdout] 23  | super::impl_ty_data!(TraitObjTy<'ast>, TraitObj);
[INFO] [stdout]     | ------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/user_ty.rs:35:1
[INFO] [stdout]     |
[INFO] [stdout] 35  | super::impl_ty_data!(AdtTy<'ast>, Adt);
[INFO] [stdout]     | -------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/user_ty.rs:62:1
[INFO] [stdout]     |
[INFO] [stdout] 62  | super::impl_ty_data!(GenericTy<'ast>, Generic);
[INFO] [stdout]     | ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stdout]    --> src/sem/ty.rs:142:15
[INFO] [stdout]     |
[INFO] [stdout] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stdout]     |               ^^^^^^^^^^------------
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/sem/ty/user_ty.rs:84:1
[INFO] [stdout]     |
[INFO] [stdout] 84  | super::impl_ty_data!(AliasTy<'ast>, Alias);
[INFO] [stdout]     | ------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `driver-api`
[INFO] [stdout]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/ast/expr/control_flow_expr.rs:475:22
[INFO] [stdout]     |
[INFO] [stdout] 475 |     pub fn condition(&self) -> ExprKind {
[INFO] [stdout]     |                      ^^^^^     -------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                      |
[INFO] [stdout]     |                      this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 475 |     pub fn condition(&self) -> ExprKind<'_> {
[INFO] [stdout]     |                                        ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/ast/expr/control_flow_expr.rs:536:21
[INFO] [stdout]     |
[INFO] [stdout] 536 |     pub fn iterable(&self) -> ExprKind {
[INFO] [stdout]     |                     ^^^^^     -------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 536 |     pub fn iterable(&self) -> ExprKind<'_> {
[INFO] [stdout]     |                                       ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]   --> src/ast/item/ty_alias_item.rs:42:23
[INFO] [stdout]    |
[INFO] [stdout] 42 |     pub fn aliased_ty(&self) -> Option<TyKind> {
[INFO] [stdout]    |                       ^^^^^            ------ the lifetime gets resolved as `'_`
[INFO] [stdout]    |                       |
[INFO] [stdout]    |                       this lifetime flows to the output
[INFO] [stdout]    |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]    |
[INFO] [stdout] 42 |     pub fn aliased_ty(&self) -> Option<TyKind<'_>> {
[INFO] [stdout]    |                                              ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]   --> src/ast/item/impl_item.rs:72:15
[INFO] [stdout]    |
[INFO] [stdout] 72 |     pub fn ty(&self) -> TyKind {
[INFO] [stdout]    |               ^^^^^     ------ the lifetime gets resolved as `'_`
[INFO] [stdout]    |               |
[INFO] [stdout]    |               this lifetime flows to the output
[INFO] [stdout]    |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]    |
[INFO] [stdout] 72 |     pub fn ty(&self) -> TyKind<'_> {
[INFO] [stdout]    |                               ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/ast/stmt.rs:129:16
[INFO] [stdout]     |
[INFO] [stdout] 129 |     pub fn els(&self) -> Option<ExprKind> {
[INFO] [stdout]     |                ^^^^^            -------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                |
[INFO] [stdout]     |                this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 129 |     pub fn els(&self) -> Option<ExprKind<'_>> {
[INFO] [stdout]     |                                         ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/span.rs:441:28
[INFO] [stdout]     |
[INFO] [stdout] 441 |     pub fn try_to_file_pos(&self, span_pos: SpanPos) -> Option<FilePos> {
[INFO] [stdout]     |                            ^^^^^                               ------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                            |
[INFO] [stdout]     |                            this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 441 |     pub fn try_to_file_pos(&self, span_pos: SpanPos) -> Option<FilePos<'_>> {
[INFO] [stdout]     |                                                                       ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/span.rs:447:24
[INFO] [stdout]     |
[INFO] [stdout] 447 |     pub fn to_file_pos(&self, span_pos: SpanPos) -> FilePos {
[INFO] [stdout]     |                        ^^^^^                        ------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                        |
[INFO] [stdout]     |                        this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 447 |     pub fn to_file_pos(&self, span_pos: SpanPos) -> FilePos<'_> {
[INFO] [stdout]     |                                                            ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 4.49s
[INFO] running `Command { std: "docker" "inspect" "a2917d2171549b6ba2f0a7af2e1d95e5537ab7f4cfab0614eb57f669e3c07b84", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "a2917d2171549b6ba2f0a7af2e1d95e5537ab7f4cfab0614eb57f669e3c07b84", kill_on_drop: false }`
[INFO] [stdout] a2917d2171549b6ba2f0a7af2e1d95e5537ab7f4cfab0614eb57f669e3c07b84
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/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" "+733b47ea4b1b86216f14ef56e49440c33933f230" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] 7636b584f7382484801f07061f5a2786f69b995aa1450305ad30595de5d47757
[INFO] running `Command { std: "docker" "start" "-a" "7636b584f7382484801f07061f5a2786f69b995aa1450305ad30595de5d47757", kill_on_drop: false }`
[INFO] [stderr] warning: unexpected `cfg` condition name: `marker`
[INFO] [stderr]   --> src/lib.rs:10:13
[INFO] [stderr]    |
[INFO] [stderr] 10 | #![cfg_attr(marker, warn(marker::marker_lints::not_using_has_span_trait))]
[INFO] [stderr]    |             ^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stderr]    = help: consider using a Cargo feature instead
[INFO] [stderr]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]             [lints.rust]
[INFO] [stderr]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(marker)'] }
[INFO] [stderr]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(marker)");` to the top of the `build.rs`
[INFO] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/fn_ty.rs:31:1
[INFO] [stderr]     |
[INFO] [stderr] 31  | super::impl_ty_data!(FnTy<'ast>, Fn);
[INFO] [stderr]     | ------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/fn_ty.rs:62:1
[INFO] [stderr]     |
[INFO] [stderr] 62  | super::impl_ty_data!(ClosureTy<'ast>, Closure);
[INFO] [stderr]     | ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/other_ty.rs:12:1
[INFO] [stderr]     |
[INFO] [stderr] 12  | super::impl_ty_data!(UnstableTy<'ast>, Unstable);
[INFO] [stderr]     | ------------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/prim_ty.rs:19:1
[INFO] [stderr]     |
[INFO] [stderr] 19  | super::impl_ty_data!(BoolTy<'ast>, Bool);
[INFO] [stderr]     | ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/prim_ty.rs:52:1
[INFO] [stderr]     |
[INFO] [stderr] 52  | super::impl_ty_data!(NumTy<'ast>, Num);
[INFO] [stderr]     | -------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/prim_ty.rs:82:1
[INFO] [stderr]     |
[INFO] [stderr] 82  | super::impl_ty_data!(TextTy<'ast>, Text);
[INFO] [stderr]     | ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/prim_ty.rs:97:1
[INFO] [stderr]     |
[INFO] [stderr] 97  | super::impl_ty_data!(NeverTy<'ast>, Never);
[INFO] [stderr]     | ------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/ptr_ty.rs:35:1
[INFO] [stderr]     |
[INFO] [stderr] 35  | super::impl_ty_data!(RefTy<'ast>, Ref);
[INFO] [stderr]     | -------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/ptr_ty.rs:58:1
[INFO] [stderr]     |
[INFO] [stderr] 58  | super::impl_ty_data!(RawPtrTy<'ast>, RawPtr);
[INFO] [stderr]     | -------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/ptr_ty.rs:91:1
[INFO] [stderr]     |
[INFO] [stderr] 91  | super::impl_ty_data!(FnPtrTy<'ast>, FnPtr);
[INFO] [stderr]     | ------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/sequence_ty.rs:21:1
[INFO] [stderr]     |
[INFO] [stderr] 21  | super::impl_ty_data!(TupleTy<'ast>, Tuple);
[INFO] [stderr]     | ------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/sequence_ty.rs:49:1
[INFO] [stderr]     |
[INFO] [stderr] 49  | super::impl_ty_data!(SliceTy<'ast>, Slice);
[INFO] [stderr]     | ------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/sequence_ty.rs:77:1
[INFO] [stderr]     |
[INFO] [stderr] 77  | super::impl_ty_data!(ArrayTy<'ast>, Array);
[INFO] [stderr]     | ------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/trait_ty.rs:23:1
[INFO] [stderr]     |
[INFO] [stderr] 23  | super::impl_ty_data!(TraitObjTy<'ast>, TraitObj);
[INFO] [stderr]     | ------------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/user_ty.rs:35:1
[INFO] [stderr]     |
[INFO] [stderr] 35  | super::impl_ty_data!(AdtTy<'ast>, Adt);
[INFO] [stderr]     | -------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/user_ty.rs:62:1
[INFO] [stderr]     |
[INFO] [stderr] 62  | super::impl_ty_data!(GenericTy<'ast>, Generic);
[INFO] [stderr]     | ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `driver_api`
[INFO] [stderr]    --> src/sem/ty.rs:142:15
[INFO] [stderr]     |
[INFO] [stderr] 142 |         #[cfg(feature = "driver_api")]
[INFO] [stderr]     |               ^^^^^^^^^^------------
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         help: there is a expected value with a similar name: `"driver-api"`
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/sem/ty/user_ty.rs:84:1
[INFO] [stderr]     |
[INFO] [stderr] 84  | super::impl_ty_data!(AliasTy<'ast>, Alias);
[INFO] [stderr]     | ------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: expected values for `feature` are: `driver-api`
[INFO] [stderr]     = help: consider adding `driver_api` as a feature in `Cargo.toml`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `super::impl_ty_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stderr]    --> src/ast/expr/control_flow_expr.rs:475:22
[INFO] [stderr]     |
[INFO] [stderr] 475 |     pub fn condition(&self) -> ExprKind {
[INFO] [stderr]     |                      ^^^^^     -------- the lifetime gets resolved as `'_`
[INFO] [stderr]     |                      |
[INFO] [stderr]     |                      this lifetime flows to the output
[INFO] [stderr]     |
[INFO] [stderr]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stderr] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stderr]     |
[INFO] [stderr] 475 |     pub fn condition(&self) -> ExprKind<'_> {
[INFO] [stderr]     |                                        ++++
[INFO] [stderr] 
[INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stderr]    --> src/ast/expr/control_flow_expr.rs:536:21
[INFO] [stderr]     |
[INFO] [stderr] 536 |     pub fn iterable(&self) -> ExprKind {
[INFO] [stderr]     |                     ^^^^^     -------- the lifetime gets resolved as `'_`
[INFO] [stderr]     |                     |
[INFO] [stderr]     |                     this lifetime flows to the output
[INFO] [stderr]     |
[INFO] [stderr] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stderr]     |
[INFO] [stderr] 536 |     pub fn iterable(&self) -> ExprKind<'_> {
[INFO] [stderr]     |                                       ++++
[INFO] [stderr] 
[INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stderr]   --> src/ast/item/ty_alias_item.rs:42:23
[INFO] [stderr]    |
[INFO] [stderr] 42 |     pub fn aliased_ty(&self) -> Option<TyKind> {
[INFO] [stderr]    |                       ^^^^^            ------ the lifetime gets resolved as `'_`
[INFO] [stderr]    |                       |
[INFO] [stderr]    |                       this lifetime flows to the output
[INFO] [stderr]    |
[INFO] [stderr] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stderr]    |
[INFO] [stderr] 42 |     pub fn aliased_ty(&self) -> Option<TyKind<'_>> {
[INFO] [stderr]    |                                              ++++
[INFO] [stderr] 
[INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stderr]   --> src/ast/item/impl_item.rs:72:15
[INFO] [stderr]    |
[INFO] [stderr] 72 |     pub fn ty(&self) -> TyKind {
[INFO] [stderr]    |               ^^^^^     ------ the lifetime gets resolved as `'_`
[INFO] [stderr]    |               |
[INFO] [stderr]    |               this lifetime flows to the output
[INFO] [stderr]    |
[INFO] [stderr] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stderr]    |
[INFO] [stderr] 72 |     pub fn ty(&self) -> TyKind<'_> {
[INFO] [stderr]    |                               ++++
[INFO] [stderr] 
[INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stderr]    --> src/ast/stmt.rs:129:16
[INFO] [stderr]     |
[INFO] [stderr] 129 |     pub fn els(&self) -> Option<ExprKind> {
[INFO] [stderr]     |                ^^^^^            -------- the lifetime gets resolved as `'_`
[INFO] [stderr]     |                |
[INFO] [stderr]     |                this lifetime flows to the output
[INFO] [stderr]     |
[INFO] [stderr] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stderr]     |
[INFO] [stderr] 129 |     pub fn els(&self) -> Option<ExprKind<'_>> {
[INFO] [stderr]     |                                         ++++
[INFO] [stderr] 
[INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stderr]    --> src/span.rs:441:28
[INFO] [stderr]     |
[INFO] [stderr] 441 |     pub fn try_to_file_pos(&self, span_pos: SpanPos) -> Option<FilePos> {
[INFO] [stderr]     |                            ^^^^^                               ------- the lifetime gets resolved as `'_`
[INFO] [stderr]     |                            |
[INFO] [stderr]     |                            this lifetime flows to the output
[INFO] [stderr]     |
[INFO] [stderr] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stderr]     |
[INFO] [stderr] 441 |     pub fn try_to_file_pos(&self, span_pos: SpanPos) -> Option<FilePos<'_>> {
[INFO] [stderr]     |                                                                       ++++
[INFO] [stderr] 
[INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stderr]    --> src/span.rs:447:24
[INFO] [stderr]     |
[INFO] [stderr] 447 |     pub fn to_file_pos(&self, span_pos: SpanPos) -> FilePos {
[INFO] [stderr]     |                        ^^^^^                        ------- the lifetime gets resolved as `'_`
[INFO] [stderr]     |                        |
[INFO] [stderr]     |                        this lifetime flows to the output
[INFO] [stderr]     |
[INFO] [stderr] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stderr]     |
[INFO] [stderr] 447 |     pub fn to_file_pos(&self, span_pos: SpanPos) -> FilePos<'_> {
[INFO] [stderr]     |                                                            ++++
[INFO] [stderr] 
[INFO] [stderr] warning: `marker_api` (lib) generated 25 warnings
[INFO] [stderr] warning: `marker_api` (lib test) generated 25 warnings (25 duplicates)
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.04s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/marker_api-699e1ea4d48662ae)
[INFO] [stdout] 
[INFO] [stdout] running 2 tests
[INFO] [stdout] test ast::item::test::test_item_struct_size ... ok
[INFO] [stdout] test ast::expr::test::expr_struct_size ... FAILED
[INFO] [stdout] 
[INFO] [stdout] failures:
[INFO] [stdout] 
[INFO] [stdout] ---- ast::expr::test::expr_struct_size stdout ----
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] [1m[91merror[97m: expect test failed[0m
[INFO] [stdout]    [1m[34m-->[0m src/ast/expr.rs:384:43
[INFO] [stdout] 
[INFO] [stdout] You can update all `expect!` tests by running:
[INFO] [stdout] 
[INFO] [stdout]     env UPDATE_EXPECT=1 cargo test
[INFO] [stdout] 
[INFO] [stdout] To update a single test, place the cursor on `expect` token and use `run` feature of rust-analyzer.
[INFO] [stdout] 
[INFO] [stdout] [1mExpect[0m:
[INFO] [stdout] ----
[INFO] [stdout] 40
[INFO] [stdout] ----
[INFO] [stdout] 
[INFO] [stdout] [1mActual[0m:
[INFO] [stdout] ----
[INFO] [stdout] 48
[INFO] [stdout] ----
[INFO] [stdout] 
[INFO] [stdout] [1mDiff[0m:
[INFO] [stdout] ----
[INFO] [stdout] 4[4m[31m0[0m[4m[32m8[0m
[INFO] [stdout] ----
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] failures:
[INFO] [stdout]     ast::expr::test::expr_struct_size
[INFO] [stdout] 
[INFO] [stdout] test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr] error: test failed, to rerun pass `--lib`
[INFO] running `Command { std: "docker" "inspect" "7636b584f7382484801f07061f5a2786f69b995aa1450305ad30595de5d47757", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "7636b584f7382484801f07061f5a2786f69b995aa1450305ad30595de5d47757", kill_on_drop: false }`
[INFO] [stdout] 7636b584f7382484801f07061f5a2786f69b995aa1450305ad30595de5d47757
