-
Notifications
You must be signed in to change notification settings - Fork 14
Update report results #323
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
Update report results #323
Conversation
d3d7d29 to
6d54472
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/437c3a065d494f3292300d6981aed929 ❌ telemetry-openstack-meta-content-provider-master FAILURE in 8m 34s |
|
recheck |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/7ece3e62fb0649a3a6c95ab1424d601b ❌ telemetry-openstack-meta-content-provider-master FAILURE in 8m 10s |
|
recheck |
6d54472 to
f4c6611
Compare
myadla
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.
lgtm
f4c6611 to
a370a7c
Compare
Previously, report_result.yml only checked for testcase failures but ignored errors in the JUnit XML output. This meant that tests could error out without causing the CI job to fail. This change adds: - Extraction of 'errors' count from XML testsuites - Failure task that triggers when errors > 0 This ensures both failures and errors in testcases are properly reported and cause the CI job to fail as expected.
a370a7c to
6a16946
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/baa9464c3f1b44be8203d101203c5a00 ✔️ telemetry-openstack-meta-content-provider-master SUCCESS in 2h 06m 09s |
|
recheck |
No description provided.