OCPBUGS-57019 OCPBUGS-56956, OPRUN-3914: [Default Catalog Consistency Test]: fix junit output format to allow generate xml #366

camilamacedo86 · 2025-06-02T08:24:56Z

See: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_operator-framework-operator-controller/366/pull-ci-openshift-operator-framework-operator-controller-main-default-catalog-consistency/1929498213128081408/artifacts/default-catalog-consistency/default-catalog-tests/artifacts/junit_olm.xml

/cherrypick release-4.19 release-4.18 release-4.17

openshift-ci-robot · 2025-06-02T08:25:19Z

@camilamacedo86: This pull request references Jira Issue OCPBUGS-56956, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.0) matches configured target version for branch (4.20.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2025-06-02T09:17:45Z

@camilamacedo86: This pull request references Jira Issue OCPBUGS-56956, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.0) matches configured target version for branch (4.20.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references OPRUN-3914 which is a valid jira issue.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

…ut format to allow generate xml

openshift-ci-robot · 2025-06-02T12:25:20Z

@camilamacedo86: This pull request references Jira Issue OCPBUGS-56956, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.0) matches configured target version for branch (4.20.0)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references OPRUN-3914 which is a valid jira issue.

In response to this:

/hold until get approval from TRT team

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci · 2025-06-02T14:02:58Z

@camilamacedo86: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/okd-scos-e2e-aws-ovn	`62634a6`	link	false	`/test okd-scos-e2e-aws-ovn`

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

openshift-ci-robot · 2025-06-02T14:15:51Z

@camilamacedo86: This pull request references Jira Issue OCPBUGS-56956, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.0) matches configured target version for branch (4.20.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

This pull request references OPRUN-3914 which is a valid jira issue.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2025-06-02T14:17:15Z

@camilamacedo86: This pull request references Jira Issue OCPBUGS-56956, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.0) matches configured target version for branch (4.20.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

This pull request references OPRUN-3914 which is a valid jira issue.

In response to this:

See: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_operator-framework-operator-controller/366/pull-ci-openshift-operator-framework-operator-controller-main-default-catalog-consistency/1929498213128081408/artifacts/default-catalog-consistency/default-catalog-tests/artifacts/junit_olm.xml

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

neisw · 2025-06-02T15:07:59Z

The naming / system-err output doesn't look right to me but its up to the approvers here to determine if it is correct.

<testcase name="[It] Check Catalog Consistency validates image: certified-operator-index" classname="Validate Catalog Test Suite" status="passed" time="10.84212816">
<system-err>
> Enter [It] validates image: certified-operator-index - /go/src/github.com/openshift/operator-framework-operator-controller/openshift/default-catalog-consistency/test/validate/suite_test.go:54 @ 06/02/25 11:25:12.184 STEP: Validating image: registry.redhat.io/redhat/certified-operator-index:v4.19 - /go/src/github.com/openshift/operator-framework-operator-controller/openshift/default-catalog-consistency/test/validate/suite_test.go:56 @ 06/02/25 11:25:12.184 < Exit [It] validates image: certified-operator-index - /go/src/github.com/openshift/operator-framework-operator-controller/openshift/default-catalog-consistency/test/validate/suite_test.go:54 @ 06/02/25 11:25:23.026 (10.842s)
</system-err>
</testcase>

openshift-ci-robot · 2025-06-02T15:40:36Z

@camilamacedo86: This pull request references Jira Issue OCPBUGS-56956, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.0) matches configured target version for branch (4.20.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

This pull request references OPRUN-3914 which is a valid jira issue.

In response to this:

See: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_operator-framework-operator-controller/366/pull-ci-openshift-operator-framework-operator-controller-main-default-catalog-consistency/1929498213128081408/artifacts/default-catalog-consistency/default-catalog-tests/artifacts/junit_olm.xml

/cherrypick release-4.19 release-4.18 release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

camilamacedo86 · 2025-06-02T15:41:43Z

Hi @neisw

You are looking at the extra info that is provided see that it has the info that you are looking for:

<testsuite name="Validate Catalog Test Suite"
package="/go/src/github.com/openshift/operator-framework-operator-controller/openshift/default-catalog-consistency/test/validate" 
tests="4" 
disabled="0" 
skipped="0" 
errors="0" 
failures="0" 
time="54.926639751" 
timestamp="2025-06-02T11:25:12">

neisw · 2025-06-02T20:01:48Z

Hi @camilamacedo86, yes I was just pointing out that it seemed odd to have [It] and extra info being output in system-err. But I'm not an approver here so I will leave it to that group to review.

camilamacedo86 · 2025-06-02T23:45:52Z

@perdasilva @thetechnick @tmshort @rashmigottipati @anik120 Could you give a hand on this one so we can move forward?

perdasilva · 2025-06-03T07:18:45Z

/approve

openshift-ci · 2025-06-03T07:19:15Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, perdasilva

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~DOWNSTREAM_OWNERS~~ [perdasilva]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

perdasilva · 2025-06-03T07:19:30Z

/lgtm

openshift-ci-robot · 2025-06-03T14:01:48Z

@camilamacedo86: Jira Issue OCPBUGS-56956: All pull requests linked via external trackers have merged:

openshift/operator-framework-operator-controller#366

Jira Issue OCPBUGS-56956 has been moved to the MODIFIED state.

In response to this:

See: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_operator-framework-operator-controller/366/pull-ci-openshift-operator-framework-operator-controller-main-default-catalog-consistency/1929498213128081408/artifacts/default-catalog-consistency/default-catalog-tests/artifacts/junit_olm.xml

/cherrypick release-4.19 release-4.18 release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-cherrypick-robot · 2025-06-03T14:02:34Z

@camilamacedo86: new pull request created: #369

In response to this:

See: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_operator-framework-operator-controller/366/pull-ci-openshift-operator-framework-operator-controller-main-default-catalog-consistency/1929498213128081408/artifacts/default-catalog-consistency/default-catalog-tests/artifacts/junit_olm.xml

/cherrypick release-4.19 release-4.18 release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

openshift-ci-robot · 2025-06-04T18:33:20Z

@camilamacedo86: Jira Issue OCPBUGS-57019: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

openshift/operator-framework-operator-controller#369 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-57019 has not been moved to the MODIFIED state.

Jira Issue OCPBUGS-56956 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

In response to this:

See: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_operator-framework-operator-controller/366/pull-ci-openshift-operator-framework-operator-controller-main-default-catalog-consistency/1929498213128081408/artifacts/default-catalog-consistency/default-catalog-tests/artifacts/junit_olm.xml

/cherrypick release-4.19 release-4.18 release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

camilamacedo86 changed the title ~~UPSTREAM: <carry>: [Default Catalog Consistency Test]: fix junit output format to allow generate xml~~ OCPBUGS-56956: UPSTREAM: <carry>: [Default Catalog Consistency Test]: fix junit output format to allow generate xml Jun 2, 2025

openshift-ci bot requested review from rashmigottipati and thetechnick June 2, 2025 08:25

openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Jun 2, 2025

openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jun 2, 2025

camilamacedo86 changed the title ~~OCPBUGS-56956: UPSTREAM: <carry>: [Default Catalog Consistency Test]: fix junit output format to allow generate xml~~ WIP: OCPBUGS-56956: UPSTREAM: <carry>: [Default Catalog Consistency Test]: fix junit output format to allow generate xml Jun 2, 2025

openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 2, 2025

camilamacedo86 force-pushed the fix-junit branch from 20be3f1 to b6c9e53 Compare June 2, 2025 11:05

UPSTREAM: <carry>: [Default Catalog Consistency Test]: fix junit outp…

62634a6

…ut format to allow generate xml

camilamacedo86 force-pushed the fix-junit branch from b6c9e53 to 62634a6 Compare June 2, 2025 11:19

openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 2, 2025

camilamacedo86 changed the title ~~OCPBUGS-56956, OPRUN-3914: UPSTREAM: <carry>: [Default Catalog Consistency Test]: fix junit output format to allow generate xml~~ OCPBUGS-56956, OPRUN-3914: [Default Catalog Consistency Test]: fix junit output format to allow generate xml Jun 2, 2025

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 3, 2025

openshift-ci bot assigned perdasilva Jun 3, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 3, 2025

openshift-merge-bot bot merged commit 3e1e9be into openshift:main Jun 3, 2025
10 of 11 checks passed

openshift-cherrypick-robot mentioned this pull request Jun 3, 2025

[release-4.19] OCPBUGS-57019, OPRUN-3914: [Default Catalog Consistency Test]: fix junit output format to allow generate xml #369

Closed

camilamacedo86 mentioned this pull request Jun 4, 2025

[release-4.19] OCPBUGS-57086: [Default Catalog Consistency Test]: Cherry-Picks up 4.17 #374

Open

camilamacedo86 changed the title ~~OCPBUGS-56956, OPRUN-3914: [Default Catalog Consistency Test]: fix junit output format to allow generate xml~~ OCPBUGS-57019 OCPBUGS-56956, OPRUN-3914: [Default Catalog Consistency Test]: fix junit output format to allow generate xml Jun 4, 2025

OCPBUGS-57019 OCPBUGS-56956, OPRUN-3914: [Default Catalog Consistency Test]: fix junit output format to allow generate xml #366

OCPBUGS-57019 OCPBUGS-56956, OPRUN-3914: [Default Catalog Consistency Test]: fix junit output format to allow generate xml #366

Uh oh!

Conversation

camilamacedo86 commented Jun 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Jun 2, 2025

Uh oh!

openshift-ci-robot commented Jun 2, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Jun 2, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci bot commented Jun 2, 2025

Uh oh!

openshift-ci-robot commented Jun 2, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Jun 2, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

neisw commented Jun 2, 2025

Uh oh!

openshift-ci-robot commented Jun 2, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

camilamacedo86 commented Jun 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

neisw commented Jun 2, 2025

Uh oh!

camilamacedo86 commented Jun 2, 2025

Uh oh!

perdasilva commented Jun 3, 2025

Uh oh!

openshift-ci bot commented Jun 3, 2025

Uh oh!

perdasilva commented Jun 3, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Jun 3, 2025

Uh oh!

openshift-cherrypick-robot commented Jun 3, 2025

Uh oh!

openshift-ci-robot commented Jun 4, 2025

Uh oh!

Uh oh!

camilamacedo86 commented Jun 2, 2025 •

edited

Loading

openshift-ci-robot commented Jun 2, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Jun 2, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Jun 2, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Jun 2, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Jun 2, 2025 •

edited by openshift-ci bot

Loading

camilamacedo86 commented Jun 2, 2025 •

edited

Loading