Uh oh!
There was an error while loading. Please reload this page.
Ensure edition lints and internal lints are enabled with deny-warnings=false - #64098
Conversation
rust-highfive
commented
Sep 2, 2019
(rust_highfive has picked a reviewer for you, use r? to override) |
alexcrichton
commented
Sep 3, 2019
While you're touching this code, would you be up for tweaking how this is handled? Ideally this would be removed from |
Mark-Simulacrum
commented
Sep 3, 2019
We don't set this for external tools (submodules) and I'd rather not thread that information through into |
Mark-Simulacrum
commented
Sep 3, 2019
It also looks like |
Uh oh!
There was an error while loading. Please reload this page.
1dbc772 to
6f959faComparealexcrichton
commented
Sep 4, 2019
We already have a |
Mark-Simulacrum
commented
Sep 4, 2019
Yeah, I think it might be easiest to just add the tool type (submodule or not) to the Mode enum; I do think it makes some sense to try to deny warnings for the in-tree tools. I'll take a look at that in a bit. |
We never allowed the warnings, only made them not denied.
6f959fa to
a2384cbCompareMark-Simulacrum
commented
Sep 4, 2019
Okay, moved most of the warning code out. Some of it is dependent on the specific crate we're compiling which means we can't actually move it out unfortunately, not sure if we can do anything about that though :/ |
alexcrichton
commented
Sep 4, 2019
@bors: r+ |
bors
commented
Sep 4, 2019
📌 Commit a2384cb has been approved by |
…crichton Ensure edition lints and internal lints are enabled with deny-warnings=false Previously we only passed the deny command line flags if deny-warnings was enabled, but now we either pass -W... or -D... for each of the flags as appropriate. This is also a breaking change to x.py as it changes `--warnings=allow` to `--warnings=warn` which is what that flag actually did; we don't have an allow warnings mode.
…crichton Ensure edition lints and internal lints are enabled with deny-warnings=false Previously we only passed the deny command line flags if deny-warnings was enabled, but now we either pass -W... or -D... for each of the flags as appropriate. This is also a breaking change to x.py as it changes `--warnings=allow` to `--warnings=warn` which is what that flag actually did; we don't have an allow warnings mode.
Centril
commented
Sep 5, 2019
Failed in #64168 (comment), @bors r- |
bors
commented
Sep 5, 2019
📌 Commit c6f868f has been approved by |
…crichton Ensure edition lints and internal lints are enabled with deny-warnings=false Previously we only passed the deny command line flags if deny-warnings was enabled, but now we either pass -W... or -D... for each of the flags as appropriate. This is also a breaking change to x.py as it changes `--warnings=allow` to `--warnings=warn` which is what that flag actually did; we don't have an allow warnings mode.
Rollup of 9 pull requests Successful merges: - #64067 (Remove no-prefer-dynamic from valgrind tests) - #64078 (compiletest: disable -Aunused for run-pass tests) - #64096 (Fix regex replacement in theme detection) - #64098 (Ensure edition lints and internal lints are enabled with deny-warnings=false) - #64166 (Better way of conditioning the sanitizer builds) - #64189 (annotate-snippet emitter: Deal with multispans from macros, too) - #64202 (Fixed grammar/style in some error messages) - #64206 (annotate-snippet emitter: Update an issue number) - #64208 (it's more pythonic to use 'is not None' in python files) Failed merges: r? @ghost
Centril
commented
Sep 6, 2019
Centril
commented
Sep 6, 2019
@bors rollup=never |
Centril
commented
Sep 6, 2019
c6f868f to
fda251bCompareMark-Simulacrum
commented
Sep 6, 2019
Determined the cause of the problem. The dist-various-2 builder uses r? @alexcrichton on this decision |
alexcrichton
commented
Sep 6, 2019
@bors: r+ |
bors
commented
Sep 6, 2019
📌 Commit fda251b has been approved by |
…crichton Ensure edition lints and internal lints are enabled with deny-warnings=false Previously we only passed the deny command line flags if deny-warnings was enabled, but now we either pass -W... or -D... for each of the flags as appropriate. This is also a breaking change to x.py as it changes `--warnings=allow` to `--warnings=warn` which is what that flag actually did; we don't have an allow warnings mode.
…crichton Ensure edition lints and internal lints are enabled with deny-warnings=false Previously we only passed the deny command line flags if deny-warnings was enabled, but now we either pass -W... or -D... for each of the flags as appropriate. This is also a breaking change to x.py as it changes `--warnings=allow` to `--warnings=warn` which is what that flag actually did; we don't have an allow warnings mode.
…crichton Ensure edition lints and internal lints are enabled with deny-warnings=false Previously we only passed the deny command line flags if deny-warnings was enabled, but now we either pass -W... or -D... for each of the flags as appropriate. This is also a breaking change to x.py as it changes `--warnings=allow` to `--warnings=warn` which is what that flag actually did; we don't have an allow warnings mode.
Rollup of 7 pull requests Successful merges: - #64023 (libstd fuchsia fixes) - #64098 (Ensure edition lints and internal lints are enabled with deny-warnings=false) - #64139 (Migrate internal diagnostic registration to macro_rules) - #64226 (Aggregation of cosmetic changes made during work on REPL PRs: libsyntax) - #64227 (Aggregation of cosmetic changes made during work on REPL PRs: librustc) - #64235 (Upgrade env_logger to 0.6) - #64258 (compiletest: Match suffixed environments) Failed merges: r? @ghost
Previously we only passed the deny command line flags if deny-warnings was enabled, but now we either pass -W... or -D... for each of the flags as appropriate.
This is also a breaking change to x.py as it changes
--warnings=allowto--warnings=warnwhich is what that flag actually did; we don't have an allow warnings mode.