Bug 1811020

Summary: CSI certification tests count success as failures
Product: OpenShift Container Platform Reporter: Jan Safranek <jsafrane>
Component: StorageAssignee: Jan Safranek <jsafrane>
Status: CLOSED ERRATA QA Contact: Qin Ping <piqin>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, lxia
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1811088 (view as bug list) Environment:
Last Closed: 2020-07-13 17:18:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1811088    

Description Jan Safranek 2020-03-06 12:46:09 UTC
Description of problem:

JUinit output of our csi certification suite counts successful tests as failures.

stdout from the openshift-tests container
43 pass, 106 skip (9m11s)

JUnit output:
<testsuite name="openshift-tests" tests="106" skipped="106" failures="43" time="551">

(failures="43" is wrong, it's nr. of successes)


Version-Release number of selected component (if applicable):
quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:376b0eafdbba3c238c214355850a3387a444b10bd651eb1c7bf3efda753689c4


How reproducible:
always

Steps to Reproduce:
See result of any pull-ci-openshift-origin-master-e2e-aws-csi job in CI, for example: https://storage.googleapis.com/origin-ci-test/pr-logs/pull/24627/pull-ci-openshift-origin-master-e2e-aws-csi/178/artifacts/e2e-aws-csi/junit/junit_e2e_20200305-211409.xml

Actual results:
The tests passed, but records "44" failures in JUnit XML:

<testsuite name="openshift-tests" tests="107" skipped="106" failures="44" time="388">


Expected results:
failures="0" (on a successful test run)

Comment 5 errata-xmlrpc 2020-07-13 17:18:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409