Skip to content

NO-ISSUE: Increase timeout + interval for OCL test cleanup#5732

Open
umohnani8 wants to merge 2 commits intoopenshift:mainfrom
umohnani8:fix-e2e-ocl-intermittent-failures
Open

NO-ISSUE: Increase timeout + interval for OCL test cleanup#5732
umohnani8 wants to merge 2 commits intoopenshift:mainfrom
umohnani8:fix-e2e-ocl-intermittent-failures

Conversation

@umohnani8
Copy link
Contributor

We keep hitting the rate limiter intermittently so
increase the interval between polling and the overall
timeout for the cleanup process to avoid this from
happening.

Have 2 commits as one is for the initial mono OCL test suite and the other is for the sharded OCL test suite. We will backport the fixes for the mono-OCL test suite so that is why I have those 2 separated into different commits.

We keep hitting the rate limiter while cleaning up,
so increase the timeout to give our tests more time
to cleanup without hitting the rate limiter or timing out.

Signed-off-by: Urvashi <umohnani@redhat.com>
We keep hitting the rate limiter intermittently so
increase the interval between polling and the overall
timeout for the cleanup process to avoid this from
happening.

Signed-off-by: Urvashi <umohnani@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 3, 2026
@openshift-ci-robot
Copy link
Contributor

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

Details

In response to this:

We keep hitting the rate limiter intermittently so
increase the interval between polling and the overall
timeout for the cleanup process to avoid this from
happening.

Have 2 commits as one is for the initial mono OCL test suite and the other is for the sharded OCL test suite. We will backport the fixes for the mono-OCL test suite so that is why I have those 2 separated into different commits.

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 requested review from pablintino and yuqi-zhang March 3, 2026 16:26
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 3, 2026
Copy link
Member

@isabella-janssen isabella-janssen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: isabella-janssen, umohnani8

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

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [isabella-janssen,umohnani8]

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

@umohnani8
Copy link
Contributor Author

/retest

2 similar comments
@umohnani8
Copy link
Contributor Author

/retest

@umohnani8
Copy link
Contributor Author

/retest

@umohnani8
Copy link
Contributor Author

/test e2e-gcp-op-ocl-part2

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 6, 2026

@umohnani8: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants