-
Notifications
You must be signed in to change notification settings - Fork 390
make CI failures easier to interpret #3399
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
@bors r+ |
make CI failures easier to interpret RUST_BACKTRACE=1 means we show 2 backtraces that are almost always irrelevant: from ui_test and from the miri script. Instead let's set the env var inside the test harness so we see backtraces of Miri ICEing but nothing else.
Oh lol, I force-pushed after approval and bors picked that up... |
@@ -223,14 +227,15 @@ fn ui( | |||
with_dependencies: Dependencies, | |||
tmpdir: &Path, | |||
) -> Result<()> { | |||
let msg = format!("## Running ui tests in {path} against miri for {target}"); | |||
let msg = format!("## Running ui tests in {path} for {target}"); |
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 "against miri" part is a leftover from ancient times when we also ran these tests in rustc.
make CI failures easier to interpret RUST_BACKTRACE=1 means we show 2 backtraces that are almost always irrelevant: from ui_test and from the miri script. Instead let's set the env var inside the test harness so we see backtraces of Miri ICEing but nothing else.
@bors r+ |
☀️ Test successful - checks-actions |
RUST_BACKTRACE=1 means we show 2 backtraces that are almost always irrelevant: from ui_test and from the miri script. Instead let's set the env var inside the test harness so we see backtraces of Miri ICEing but nothing else.