#`trick_rust_analyzer_into_highlighting_interpolated_bits` CI error

4 messages · Page 1 of 1 (latest)

pale trench
#

FIX: cargo update

Running cargo r -p ci on any branch of bevy fails with a bunch of errors that I don't understand (log below). compile, test and doc work fine on their own, but adding lints causes the error. I've tried on nightly and stable, unsure what to do next.

The error is repeated for 30 different CI scripts.

Help appreciated 🙂

#
warning: unexpected `cfg` condition name: `trick_rust_analyzer_into_highlighting_interpolated_bits`
  --> tools/ci/src/commands/bench_check.rs:13:13
   |
13 | /             cmd!(
14 | |                 sh,
15 | |                 "cargo check --benches --target-dir ../target --manifest-path ./benches/Cargo.toml"
16 | |             ),
   | |_____________^
   |
   = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `docsrs_dep`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
   = help: consider using a Cargo feature instead
   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
            [lints.rust]
            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(trick_rust_analyzer_into_highlighting_interpolated_bits)'] }
   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(trick_rust_analyzer_into_highlighting_interpolated_bits)");` to the top of the `build.rs`
   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
   = note: requested on the command line with `-W unexpected-cfgs`
   = note: this warning originates in the macro `cmd` (in Nightly builds, run with -Z macro-backtrace for more info)
#

I've narrowed it down to an xshell issue, ran cargo update and recompiling now...

#

Yup that fixed it, I'll leave this here for future reference as that error message was horrid