-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
ICEs should print the top of the query stack #76920
ICEs should print the top of the query stack #76920
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @oli-obk (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
This should affect a ui test, did you Also I only now understand your question... Yea we should keep printing the full stack if |
ahh no sorry I forgot, I will add git hook to run it automatically before every commit ok I will fix the change about |
I think you meant to link to #70953 |
cc #76356 |
thanks |
Note that for ui tests you do need a full build, so |
sorry anyone knows that why the test of gnu-llvm-8 fails? |
@@ -1,3 +1,5 @@ | |||
query stack during panic: |
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.
Please filter this out with more filter instructions in the corresponding .rs
file, the same with all the other proc macros.
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.
sorry I did not understand that what should I do
can you please explain more?
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.
Did it not disappear after switching the condition?
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.
In case it's still there after the change, what I meant was to add more of the regexes like
rust/src/test/ui/proc-macro/invalid-punct-ident-1.rs
Lines 5 to 11 in 767e84a
// normalize-stderr-test "thread.*panicked.*proc_macro_server.rs.*\n" -> "" | |
// normalize-stderr-test "note:.*RUST_BACKTRACE=1.*\n" -> "" | |
// normalize-stderr-test "\nerror: internal compiler error.*\n\n" -> "" | |
// normalize-stderr-test "note:.*unexpectedly panicked.*\n\n" -> "" | |
// normalize-stderr-test "note: we would appreciate a bug report.*\n\n" -> "" | |
// normalize-stderr-test "note: compiler flags.*\n\n" -> "" | |
// normalize-stderr-test "note: rustc.*running on.*\n\n" -> "" |
Basically I think you can add
// normalize-stderr-test "query stack during panic:\n" -> ""
// normalize-stderr-test "end of query stack:\n" -> ""
and these lines should disappear
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.
ok got it, thanks, I will fix now
@hosseind75 it prints what the failures were:
|
yeah, I got that what It means now, thanks |
@jyn514 about |
You can also patch https://github.com/rust-lang/rust/blob/master/src/test/ui/proc-macro/load-panic-backtrace.rs to filter out the new messages. Is it not showing up when you run locally? |
no, I ran this test locally but the ICEs messages did not show up In |
Is the test run at all, or do you get a "skipped" message? Maybe it's skipped on your platform? |
aah yeah, I ran it now and it is ignoring |
I think you can test this with |
☔ The latest upstream changes (presumably #70743) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
@jyn514 the test failure messages is like the messages that I got when I had automatic x.py check running |
@hosseind75 try |
See also rust-lang/rustc-dev-guide#890 which is pretty detailed. |
…ack message when RUST_BACKTRACE=0
>>>>>>> 15827338aa231fd408561bf5db8d8eea85d1a51a | ||
======= | ||
if num_frames == Some(i) { | ||
>>>>>>> 15827338aa231fd408561bf5db8d8eea85d1a51a |
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.
This is a messed up rebase.
@@ -14,4 +14,4 @@ note: compiler flags: FLAGS | |||
query stack during panic: | |||
#0 [check_match] match-checking `main` | |||
#1 [analysis] running analysis passes on this crate | |||
we're just showing a limited slice of the query stack | |||
we're just showing a limited slice of the query stack |
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.
I think this will cause bors to fail again, is there a reason you removed it?
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.
you mean about new line? @jyn514
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.
Yeah, you removed the newline.
guys a problem happened for my acount and I forced to create new acount, sorry, I opened a new PR for this issue , it is the link #77493 |
…_the_top_of_the_query_stack, r=oli-obk ICEs should always print the top of the query stack see rust-lang#76920
…_the_top_of_the_query_stack, r=oli-obk ICEs should always print the top of the query stack see rust-lang#76920
…_the_top_of_the_query_stack, r=oli-obk ICEs should always print the top of the query stack see rust-lang#76920
…_the_top_of_the_query_stack, r=oli-obk ICEs should always print the top of the query stack see rust-lang#76920
see #76920
r? @oli-obk