-
Notifications
You must be signed in to change notification settings - Fork 26
openqa-bats-review: Process JUnit XML instead of TAP #469
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
d3flex
left a comment
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.
Can you remind me why openqa-bats-review has to be in this repo and not in osado?
To be run as a post hook script, but now we have this issue: https://suse.slack.com/archives/C02CANHLANP/p1758633673618689 |
2136a2c to
98646ef
Compare
35bc896 to
272918a
Compare
bbeba2d to
e87cb2b
Compare
e87cb2b to
9660cd0
Compare
okurz
left a comment
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.
OBS checks don't work due to the fork's repo name differing. Merging manually.
|
It seems this is now failing in OBS: We should revert unless you have a quick fix for this... |
BATS tests are now producing both JUnit XML (for openQA processing) and TAP logs for human consumption. We have other upstream tests that use only JUnit XML that would benefit from this post fail hook:
docker_testsuite&podman_e2e.Related ticket: https://progress.opensuse.org/issues/186786
TODO
openqa-label-known-issues-and-investigate-hookto check testsuite names instead ofBATS_PACKAGE.In another PR: restart jobs and don't rely on RETRY.
Verification runs: