You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This allows users to either
- hide warnings (#14258)
- error on warnings (#8424)
`build.warnings` is setup to mirror the behavior of `RUSTFLAGS=-Dwarnings`,
including
- only errors for lint warnings and not hard warnings
- only errors for local warnings and not non-local warnings visible with
`--verbose --verbose`
- stop the build without `--keep-going`
These conditions were not originally met and also came as feedback from
rust-lang/rust which has been dogfooding this since the merge of rust-lang/rust#148332.
Things are a bit different with `RUSTFLAGS=-Awarnings`:
- Hard warnings are hidden for rustc but not cargo (rustc seems in the
wrong imo)
- In particular, we shouldn't mask the edition warning for Cargo
Script
- both hide the warning summary line (number of warnings per crate)
- both hide non-local warnings for `--verbose --verbose`
One design constraint we are operating on with this is that changing
`build.warnings` should not cause a rebuild, unlike a `RUSTFLAGS`
solution.
Closes#14802
- CI can fail due to new toolchain versions because there are limited compatibility guarantees around warnings.
228
+
Consider pinning the toolchain version with an automated job that creates a PR to upgrade the toolchain on new releases.
229
+
- Balance between exhaustiveness and turnaround time in selecting the combinations of platforms, features, and package/build-target combinations to check
230
+
- Some CI systems have direct integration for reporting lints, e.g. using [`clippy-sarif`] with GitHub
0 commit comments