-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[COMPILETEST-UNTANGLE 2/N] Make some compiletest errors/warnings/help more visually obvious #143230
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
Merged
+84
−38
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
//! Collection of diagnostics helpers for `compiletest` *itself*. | ||
#[macro_export] | ||
macro_rules! fatal { | ||
($($arg:tt)*) => { | ||
let status = ::colored::Colorize::bright_red("FATAL: "); | ||
let status = ::colored::Colorize::bold(status); | ||
eprint!("{status}"); | ||
eprintln!($($arg)*); | ||
// This intentionally uses a seemingly-redundant panic to include backtrace location. | ||
// | ||
// FIXME: in the long term, we should handle "logic bug in compiletest itself" vs "fatal | ||
// user error" separately. | ||
panic!("fatal error"); | ||
}; | ||
} | ||
|
||
#[macro_export] | ||
macro_rules! error { | ||
($($arg:tt)*) => { | ||
let status = ::colored::Colorize::red("ERROR: "); | ||
let status = ::colored::Colorize::bold(status); | ||
eprint!("{status}"); | ||
eprintln!($($arg)*); | ||
}; | ||
} | ||
|
||
#[macro_export] | ||
macro_rules! warning { | ||
($($arg:tt)*) => { | ||
let status = ::colored::Colorize::yellow("WARNING: "); | ||
let status = ::colored::Colorize::bold(status); | ||
eprint!("{status}"); | ||
eprintln!($($arg)*); | ||
}; | ||
} | ||
|
||
#[macro_export] | ||
macro_rules! help { | ||
($($arg:tt)*) => { | ||
let status = ::colored::Colorize::cyan("HELP: "); | ||
let status = ::colored::Colorize::bold(status); | ||
eprint!("{status}"); | ||
eprintln!($($arg)*); | ||
}; | ||
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
std::panic::resume_unwind(Box::new(()))
would also work to silently panic (no panic message and no backtrace)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.
Hm right. Though a backtrace might be useful in this case, mostly for panic location?
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.
(Not that randomly panicking in random places is ideal, but)
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.
At least some of the cases of
fatal!()
are user errors, not bugs in compiletest itself. For user errors backtraces aren't that useful.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.
Changed to
std::panic::resume_unwind(Box::new(()))
instead.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.
Backtraces are useful in general to make debugging easier though, even if it's a user error, users might sometimes want to take a look at compiletest's source code to see what exactly is triggering the panic, and what should they change (it might not always be obvious from the error message).
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.
That is true. I think I'll retain the explicit panic for the backtrace location at least for now. Eventually, though, I'd like the user error vs compiletest logic bug to be handled differently.
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'm going with the explicit panic for the short-term.