Skip to content

Mark unstable tests as failures in JUnit output #136

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.

Sign up for GitHub

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
timwoj merged 1 commit into from
Jun 1, 2026
Merged

Mark unstable tests as failures in JUnit output #136

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions btest
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2169,7 +2169,6 @@ class XMLReport(OutputHandler):
RESULT_PASS = "pass"
RESULT_FAIL = "failure"
RESULT_SKIP = "skipped"
RESULT_UNSTABLE = "unstable"

def __init__(self, options, xmlfile):
"""Output handler for producing an XML report of test results.
Expand Down Expand Up @@ -2252,7 +2251,8 @@ class XMLReport(OutputHandler):
self.addTestResult(test, self.RESULT_FAIL)

def testUnstable(self, test, msg):
self.addTestResult(test, self.RESULT_UNSTABLE)
# JUnit has no concept of flaky tests, report them as failures.
self.testFailed(test, msg)

def testSkipped(self, test, msg):
self.addTestResult(test, self.RESULT_SKIP)
Expand Down
Loading