Skip to content

[release-4.22] OCPBUGS-83546: Fix Cypress test timeouts by using correct timeout option#16292

Open
openshift-cherrypick-robot wants to merge 2 commits intoopenshift:release-4.22from
openshift-cherrypick-robot:cherry-pick-16280-to-release-4.22
Open

[release-4.22] OCPBUGS-83546: Fix Cypress test timeouts by using correct timeout option#16292
openshift-cherrypick-robot wants to merge 2 commits intoopenshift:release-4.22from
openshift-cherrypick-robot:cherry-pick-16280-to-release-4.22

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #16280

/assign rhamilto

rhamilto and others added 2 commits April 15, 2026 20:09
Multiple Cypress integration tests were timing out in CI after 15 seconds
despite attempting to set a 300-second timeout. The tests were using
`requestTimeout` in WAIT_OPTIONS, but this option controls how long to wait
for the request to be sent, not how long to wait for the response or for the
cy.wait() command to complete.

Changed `requestTimeout` to `timeout` in all affected test files. The `timeout`
option is the correct option for controlling how long cy.wait() will wait for
route aliases to resolve.

Affected files:
- packages/integration-tests/tests/app/admission-webhook-warning-notifications.cy.ts
- packages/integration-tests/tests/app/poll-console-updates.cy.ts
- packages/integration-tests/tests/cluster-settings/channel-modal.cy.ts
- packages/integration-tests/tests/cluster-settings/update-in-progress.cy.ts
- packages/integration-tests/tests/cluster-settings/update-modal.cy.ts
- packages/integration-tests/tests/cluster-settings/updates-graph.cy.ts
- packages/integration-tests/tests/cluster-settings/upgradeable-false.cy.ts
- packages/integration-tests/tests/cluster-settings/worker-mcp-paused.cy.ts

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 15, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please ask for approval from rhamilto. For more information see the Code Review Process.

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

Details 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 component/helm Related to helm-plugin component/knative Related to knative-plugin component/olm Related to OLM component/topology Related to topology kind/cypress Related to Cypress e2e integration testing labels Apr 15, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-83446 has been cloned as Jira Issue OCPBUGS-83546. Will retitle bug to link to clone.
/retitle [release-4.22] OCPBUGS-83546: Fix Cypress test timeouts by using correct timeout option

Details

In response to this:

This is an automated cherry-pick of #16280

/assign rhamilto

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 changed the title [release-4.22] OCPBUGS-83446: Fix Cypress test timeouts by using correct timeout option [release-4.22] OCPBUGS-83546: Fix Cypress test timeouts by using correct timeout option Apr 15, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 15, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-83546, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-83446 to target a version in 4.23.0, but it targets "5.0.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

This is an automated cherry-pick of #16280

/assign rhamilto

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.

@jhadvig
Copy link
Copy Markdown
Member

jhadvig commented Apr 16, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@jhadvig: This pull request references Jira Issue OCPBUGS-83546, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-83446 to target a version in 4.23.0, but it targets "5.0.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

@jhadvig
Copy link
Copy Markdown
Member

jhadvig commented Apr 16, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@jhadvig: This pull request references Jira Issue OCPBUGS-83546, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

@jhadvig
Copy link
Copy Markdown
Member

jhadvig commented Apr 16, 2026

/jira refresh
/retest

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@jhadvig: This pull request references Jira Issue OCPBUGS-83546, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh
/retest

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
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 16, 2026

@openshift-cherrypick-robot: 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/e2e-gcp-console 55c0999 link true /test e2e-gcp-console

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

component/dev-console Related to dev-console component/helm Related to helm-plugin component/knative Related to knative-plugin component/olm Related to OLM component/topology Related to topology jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/cypress Related to Cypress e2e integration testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants