-
Notifications
You must be signed in to change notification settings - Fork 13.7k
Start reporting future breakage for ILL_FORMED_ATTRIBUTE_INPUT
in dependencies
#144544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@bors2 try
Start reporting future breakage for `ILL_FORMED_ATTRIBUTE_INPUT` in dependencies
cc @rust-lang/lang @rust-lang/lang-advisors
It seems clear to me that we should do this in any event, so let's...
@rfcbot fcp merge
Team member @traviscross has proposed to merge this. The next step is review by the rest of the tagged team members:
No concerns currently listed.
Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!
cc @rust-lang/lang-advisors: FCP proposed for lang, please feel free to register concerns.
See this document for info about what commands tagged team members can give me.
@bors try
Start reporting future breakage for `ILL_FORMED_ATTRIBUTE_INPUT` in dependencies
@craterbot check
👌 Experiment pr-144544
created and queued.
🤖 Automatically detected try build d7b15db
🔍 You can check out the queue and this experiment's details.
i️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more
@bors try cancel
Try build cancelled. Cancelled workflows:
🚧 Experiment pr-144544
is now running
i️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more
🎉 Experiment pr-144544
is completed!
📊 3 regressed and 7 fixed (672551 total)
📰 Open the summary report.
i️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more
All 3 regressions seem spurious
... r=traviscross Start reporting future breakage for `ILL_FORMED_ATTRIBUTE_INPUT` in dependencies This has been a warn lint since early 2019 and a deny-by-default lint since late 2019. We're currently transitioning some of the cases where this lint is being produced to a hard error (rust-lang#143607 rust-lang#143808 and more) So let's report this lint in all dependencies for the remaining attributes r? ````@traviscross```` ````@rustbot```` labels +I-lang-nominated +T-lang -T-compiler cc ````@jdonszelmann```` (Separate question: Why does the "Future incompatibility report" only trigger if `report_in_deps` is true, even if the future incompatibility happens in the same crate, is this correct?) This also needs a crater run, but I don't have permissions to trigger this
Rollup of 19 pull requests Successful merges: - #141624 (unstable-book: Add stubs for environment variables; document some of the important ones) - #143093 (Simplify polonius location-sensitive analysis) - #144402 (Stabilize loongarch32 inline asm) - #144403 (`tests/ui/issues/`: The Issues Strike Back [4/N]) - #144544 (Start reporting future breakage for `ILL_FORMED_ATTRIBUTE_INPUT` in dependencies) - #144739 (Use new public libtest `ERROR_EXIT_CODE` constant in rustdoc) - #145089 (Improve error output when a command fails in bootstrap) - #145112 ([win][arm64ec] Partial fix for raw-dylib-link-ordinal on Arm64EC) - #145129 ([win][arm64ec] Add `/machine:arm64ec` when linking LLVM as Arm64EC) - #145130 (improve "Documentation problem" issue template.) - #145135 (Stabilize `duration_constructors_lite` feature) - #145145 (some `derive_more` refactors) - #145147 (rename `TraitRef::from_method` to `from_assoc`) - #145156 (Override custom Cargo `build-dir` in bootstrap) - #145160 (Change days-threshold to 28 in [behind-upstream]) - #145162 (`{BTree,Hash}Map`: add "`Entry` API" section heading) - #145175 (Enable limit_rdylib_exports on Solaris) - #145187 (Fix an unstable feature comment that wasn't a doc comment) - #145191 (`suggest_borrow_generic_arg`: use the correct generic args) r? `@ghost` `@rustbot` modify labels: rollup
Seems to have failed rollup #145197 (comment)
662 For more information about an error, try `rustc --explain E0308`.
663 Future incompatibility report: Future breakage diagnostic:
664 error: valid forms for the attribute are `#[doc(hidden|inline|...)]` and `#[doc = "string"]`
- --> $DIR/malformed-attrs.rs:44:1
+ --> $DIR/malformed-attrs.rs:40:1
666 |
667 LL | #[doc]
668 | ^^^^^^
@bors r-
This comment has been minimized.
This comment has been minimized.
...ependencies Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
7bd902d
to
b2b4bd4
Compare
Was able to reproduce locally, fixed & rebased.
Because of the line numbers in the "Future incompatibility report", this is PR is likely to soft-conflict.
Don't rollup with any attribute-related PRs
@bors rollup=never (conflicts with attribute-related PRs)
@bors r+ rollup=never
☀️ Test successful - checks-actions
Approved by: traviscross
Pushing 29737cb to master...
What is this?
This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 18eeac0 (parent) -> 29737cb (this PR)
Test differences
Show 276 test diffs
276 doctest diffs were found. These are ignored, as they are noisy.
Test dashboard
Run
cargo run --manifest-path src/ci/citool/Cargo.toml -- \ test-dashboard 29737cb44beb67dbcf001ca1f11b7ec8964d8d06 --output-dir test-dashboard
And then open test-dashboard/index.html
in your browser to see an overview of all executed tests.
Job duration changes
- x86_64-apple-1: 11621.6s -> 8080.9s (-30.5%)
- dist-x86_64-apple: 8100.6s -> 9227.9s (13.9%)
- aarch64-gnu-llvm-19-1: 4089.2s -> 3616.1s (-11.6%)
- test-various: 4607.2s -> 5087.6s (10.4%)
- x86_64-apple-2: 5165.4s -> 5631.9s (9.0%)
- aarch64-apple: 5492.7s -> 5970.2s (8.7%)
- x86_64-gnu-llvm-19-1: 3330.2s -> 3619.0s (8.7%)
- dist-aarch64-apple: 5909.6s -> 5490.8s (-7.1%)
- dist-various-2: 3165.0s -> 2948.5s (-6.8%)
- aarch64-gnu: 7075.5s -> 7538.3s (6.5%)
How to interpret the job duration changes?
Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.
Finished benchmarking commit (29737cb): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary 4.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.3%, secondary -4.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 462.481s -> 464.526s (0.44%) |
Uh oh!
There was an error while loading. Please reload this page.
This has been a warn lint since early 2019 and a deny-by-default lint since late 2019.
We're currently transitioning some of the cases where this lint is being produced to a hard error (#143607 #143808 and more)
So let's report this lint in all dependencies for the remaining attributes
r? @traviscross
@rustbot labels +I-lang-nominated +T-lang -T-compiler
cc @jdonszelmann
(Separate question: Why does the "Future incompatibility report" only trigger if
report_in_deps
is true, even if the future incompatibility happens in the same crate, is this correct?)This also needs a crater run, but I don't have permissions to trigger this