Skip to content

Conversation

djoshy
Copy link
Contributor

@djoshy djoshy commented Aug 11, 2025

This test has been flakey in the past, and we opened https://issues.redhat.com/browse/OCPBUGS-48526 to track it, but its failure count has gotten frequent enough to warrant further investigation. Unsure if some recent changes have made its failure more prevalent.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 11, 2025
@openshift-ci-robot
Copy link
Contributor

@djoshy: This pull request explicitly references no jira issue.

In response to this:

This test has been flakey in the past, and we opened https://issues.redhat.com/browse/OCPBUGS-48526 to track it, but its failure count has gotten frequent enough to warrant further investigation. Unsure if some recent changes have made its failure more prevalent.

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 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 Aug 11, 2025
Copy link
Contributor

openshift-ci bot commented Aug 11, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link
Contributor

openshift-ci bot commented Aug 11, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 11, 2025
@djoshy djoshy force-pushed the fix-flakey-ocl-units branch from 960aafd to 09c7a03 Compare August 22, 2025 12:55
@djoshy
Copy link
Contributor Author

djoshy commented Aug 22, 2025

/test unit

2 similar comments
@djoshy
Copy link
Contributor Author

djoshy commented Aug 22, 2025

/test unit

@djoshy
Copy link
Contributor Author

djoshy commented Aug 22, 2025

/test unit

Copy link
Contributor

openshift-ci bot commented Aug 22, 2025

@djoshy: all tests passed!

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants