Skip to content

Conversation

@elfiesmelfie
Copy link
Collaborator

No description provided.

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.
@softwarefactory-project-zuul
Copy link

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/437c3a065d494f3292300d6981aed929

telemetry-openstack-meta-content-provider-master FAILURE in 8m 34s
⚠️ functional-tests-osp18 SKIPPED Skipped due to failed job telemetry-openstack-meta-content-provider-master
⚠️ functional-logging-tests-osp18 SKIPPED Skipped due to failed job telemetry-openstack-meta-content-provider-master

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant