Fix sorting of junit tests in presence of a timeout #8600
Merged
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.
Problem
When we timeout or when junit XML is corrupted for some reason, it can prevent us from identifying the target that failed, which causes us to default to a
None
cluster of tests.We knew this already though, and the codepath that parsed tests accounted for it. But we had missed a case.
Solution
Default to the empty string rather than
None
when sorting tests.