Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Add debug traces to failing test steps #19145
Currently, if one of the steps executed during the tests returns a non-zero exit code, we fail with the following message:
Normally, since the failing step prints an error, it's easy to identify which step failed, but in other situations (like this test build) it's hard to identify which step is failing.
For now this only prints the step that caused the failure (which is the only thing we can get at the moment), but we can use this to print additional information in the future.
This may give us some information to identify the root cause of #19089