Skip to content

Mark unstable tests as failures in JUnit output#136

Merged
timwoj merged 1 commit into
masterfrom
topic/timw/mark-unstable-tests-as-failures-in-junit-output
Jun 1, 2026
Merged

Mark unstable tests as failures in JUnit output#136
timwoj merged 1 commit into
masterfrom
topic/timw/mark-unstable-tests-as-failures-in-junit-output

Conversation

@timwoj
Copy link
Copy Markdown
Member

@timwoj timwoj commented Jun 1, 2026

The JUnit format only has tags for faiulre, error, and skipped. Our unofficial unstable tag causes problems with other tooling that reads the JUnit output, such as CircleCI's test insights.

This is related to zeek/zeek#5512

Comment thread btest Outdated
The JUnit format only has tags for faiulre, error, and skipped. Our
unofficial unstable tag causes problems with other tooling that reads
the JUnit output, such as CircleCI's test insights.
@timwoj timwoj force-pushed the topic/timw/mark-unstable-tests-as-failures-in-junit-output branch from 8b9d935 to 55ff12c Compare June 1, 2026 16:09
@timwoj timwoj merged commit 74ed391 into master Jun 1, 2026
30 of 43 checks passed
@timwoj timwoj deleted the topic/timw/mark-unstable-tests-as-failures-in-junit-output branch June 1, 2026 19:53
@awelzel
Copy link
Copy Markdown
Contributor

awelzel commented Jun 2, 2026

Technically this is a breaking change and some users might have actually relied on this. I'm okay hand-wavy saying this will not impact anyone and it was against the spec, but I'm leaving a comment here anyhow.

There's no NEWS file, but it's in CHANGES, so that's hopefully enough.

@timwoj
Copy link
Copy Markdown
Member Author

timwoj commented Jun 2, 2026

True, but the documentation for btest also says this:

-x FILE, --xml=FILE
Records test results in JUnit XML format to the given file.
If the file exists already, it is overwritten.

What we were outputting wasn't valid JUnit XML, and now it's more so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants