-
Notifications
You must be signed in to change notification settings - Fork 14k
Mention crate being analyzed in query description #147137
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
|
This PR modifies |
|
r? @nnethercote rustbot has assigned @nnethercote. Use |
| LL | const FOO: usize = FOO; | ||
| | ^^^ | ||
| = note: ...which again requires simplifying constant for the type system `FOO`, completing the cycle | ||
| = note: cycle used when running analysis passes on this crate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this line removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rest of the PR looks fine, but this is a worry, because this test looks very similar to the other tests but it is changed in a different way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An answer here is needed to unblock further progress.
@rustbot author
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After rebasing these changes went away.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your lucky day!
| error: aborting due to 1 previous error | ||
|
|
||
| For more information about this error, try `rustc --explain E0391`. | ||
| For more information about this error, try `rustc --explain E0391`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the file-ending newline removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be perfectly honest: not the faintest idea why my changes affect this test at all 😵
|
Reminder, once the PR becomes ready for a review, use |
|
☔ The latest upstream changes (presumably #148182) made this pull request unmergeable. Please resolve the merge conflicts. |
"running analysis passes on this crate" -> "running analysis passes on crate `foo`" This message is displayed in cycle errors in particular, and in some cases without any spans or any other identifiable information to determine which dependency introduced the cycle.
|
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
@bors r+ rollup |
Mention crate being analyzed in query description "running analysis passes on this crate" -> "running analysis passes on crate `foo`" This message is displayed in cycle errors in particular, and in some cases without any spans or any other identifiable information to determine which dependency introduced the cycle. Address rust-lang#74380, but we still need a test for that case in particular.
Rollup of 8 pull requests Successful merges: - #147137 (Mention crate being analyzed in query description) - #148099 (Prepare to move debugger discovery from compiletest to bootstrap) - #148194 (compiletest: Remove `cleanup_debug_info_options`) - #148199 (compiletest: Don't modify `testpaths` when creating aux contexts) - #148240 (rustc_codegen: fix musttail returns for cast/indirect ABIs) - #148247 (Remove two special cases from reachable_non_generics) - #148290 (Do not emit solver errors that contain error types) - #148362 (docs: makes a note about possible building `rustc 1.91.0 + host tools` for win7) r? `@ghost` `@rustbot` modify labels: rollup
Mention crate being analyzed in query description "running analysis passes on this crate" -> "running analysis passes on crate `foo`" This message is displayed in cycle errors in particular, and in some cases without any spans or any other identifiable information to determine which dependency introduced the cycle. Address rust-lang#74380, but we still need a test for that case in particular.
Rollup of 12 pull requests Successful merges: - #147137 (Mention crate being analyzed in query description) - #147642 (Miscellaneous const-generics-related fixes) - #147806 (Ignore test-dashboard related files) - #147947 (Implement `strip_circumfix` lib feature) - #148194 (compiletest: Remove `cleanup_debug_info_options`) - #148199 (compiletest: Don't modify `testpaths` when creating aux contexts) - #148247 (Remove two special cases from reachable_non_generics) - #148348 (dangling ptr lint cleanup) - #148357 (temporary-lifetime-extension.rs test works in all editions) - #148362 (docs: makes a note about possible building `rustc 1.91.0 + host tools` for win7) - #148367 (Use --print host-tuple to get the host) - #148374 (miri subtree update) r? `@ghost` `@rustbot` modify labels: rollup
Mention crate being analyzed in query description "running analysis passes on this crate" -> "running analysis passes on crate `foo`" This message is displayed in cycle errors in particular, and in some cases without any spans or any other identifiable information to determine which dependency introduced the cycle. Address rust-lang#74380, but we still need a test for that case in particular.
|
Investigating rollup failure in #148376 (comment): @bors try jobs=armhf-gnu |
|
⌛ Trying commit 0efeec5 with merge 950a815… To cancel the try build, run the command Workflow: https://github.com/rust-lang/rust/actions/runs/19008792157 |
Mention crate being analyzed in query description try-job: armhf-gnu
|
Failure found at #148247 (comment). @bors try cancel |
|
Try build cancelled. Cancelled workflows: |
Rollup of 9 pull requests Successful merges: - #147137 (Mention crate being analyzed in query description) - #147155 (arm-linux.md: various fixes/improvements) - #147642 (Miscellaneous const-generics-related fixes) - #147806 (Ignore test-dashboard related files) - #147947 (Implement `strip_circumfix` lib feature) - #148346 (Change cfg_trace, cfg_attr_trace symbol values) - #148348 (dangling ptr lint cleanup) - #148393 (Remove `tests/run-make/fmt-write-bloat/`) - #148400 (Better warning message for crate type unsupported by codegen backend) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of #147137 - estebank:issue-74380, r=nnethercote Mention crate being analyzed in query description "running analysis passes on this crate" -> "running analysis passes on crate `foo`" This message is displayed in cycle errors in particular, and in some cases without any spans or any other identifiable information to determine which dependency introduced the cycle. Address #74380, but we still need a test for that case in particular.
Rollup of 9 pull requests Successful merges: - rust-lang/rust#147137 (Mention crate being analyzed in query description) - rust-lang/rust#147155 (arm-linux.md: various fixes/improvements) - rust-lang/rust#147642 (Miscellaneous const-generics-related fixes) - rust-lang/rust#147806 (Ignore test-dashboard related files) - rust-lang/rust#147947 (Implement `strip_circumfix` lib feature) - rust-lang/rust#148346 (Change cfg_trace, cfg_attr_trace symbol values) - rust-lang/rust#148348 (dangling ptr lint cleanup) - rust-lang/rust#148393 (Remove `tests/run-make/fmt-write-bloat/`) - rust-lang/rust#148400 (Better warning message for crate type unsupported by codegen backend) r? `@ghost` `@rustbot` modify labels: rollup
"running analysis passes on this crate" -> "running analysis passes on crate
foo"This message is displayed in cycle errors in particular, and in some cases without any spans or any other identifiable information to determine which dependency introduced the cycle.
Address #74380, but we still need a test for that case in particular.