Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-14463: Web Terminal e2e tests are failing #12922

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

musienko-maxim
Copy link
Contributor

After investigating the flakiness of the web terminal after the first run test, I supposed that WTO could not finish the full installation. This PR add check up this on UI part

@openshift-ci openshift-ci bot added the component/dev-console Related to dev-console label Jun 22, 2023
@lokanandaprabhu
Copy link
Contributor

/retitle OCPBUGS-14463: Web Terminal e2e tests are failing

@openshift-ci openshift-ci bot changed the title Add verification for installing WTO on UI OCPBUGS-14463: Web Terminal e2e tests are failing Jun 22, 2023
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jun 22, 2023
@openshift-ci-robot
Copy link
Contributor

@musienko-maxim: This pull request references Jira Issue OCPBUGS-14463, 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.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sanketpathak

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

In response to this:

After investigating the flakiness of the web terminal after the first run test, I supposed that WTO could not finish the full installation. This PR add check up this on UI part

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/test-infra repository.

@openshift-ci openshift-ci bot requested a review from sanketpathak June 22, 2023 08:19
@lokanandaprabhu
Copy link
Contributor

/retest

1 similar comment
@musienko-maxim
Copy link
Contributor Author

/retest

@musienko-maxim musienko-maxim force-pushed the investigate-flakiness-web-terminal-adminuser branch from 796a8dc to 1ba3a47 Compare July 6, 2023 10:19
@musienko-maxim
Copy link
Contributor Author

/test e2e-gcp-console

@openshift-ci openshift-ci bot added the kind/cypress Related to Cypress e2e integration testing label Jul 6, 2023
@musienko-maxim
Copy link
Contributor Author

/test images

@musienko-maxim
Copy link
Contributor Author

/test e2e-gcp-console

@musienko-maxim musienko-maxim force-pushed the investigate-flakiness-web-terminal-adminuser branch from 6722acf to 64412d1 Compare July 8, 2023 06:57
@musienko-maxim musienko-maxim force-pushed the investigate-flakiness-web-terminal-adminuser branch 2 times, most recently from fd73245 to 235d880 Compare August 3, 2023 08:25
@musienko-maxim
Copy link
Contributor Author

/test e2e-gcp-console

@lokanandaprabhu
Copy link
Contributor

/retest e2e-gcp-console

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 8, 2023

@lokanandaprabhu: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test analyze
  • /test backend
  • /test e2e-gcp-console
  • /test frontend
  • /test images

Use /test all to run all jobs.

In response to this:

/retest e2e-gcp-console

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/test-infra repository.

@lokanandaprabhu
Copy link
Contributor

/test e2e-gcp-console

1 similar comment
@lokanandaprabhu
Copy link
Contributor

/test e2e-gcp-console

@jerolimov
Copy link
Member

/retest

@jerolimov
Copy link
Member

/assign

Copy link
Member

@jerolimov jerolimov left a comment

Choose a reason for hiding this comment

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

@sanketpathak is this fine for you? can you add lgtm then?

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 16, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerolimov, musienko-maxim

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 Oct 16, 2023
@jerolimov
Copy link
Member

/assign @sanketpathak @The-Anton

@sanketpathak
Copy link
Contributor

The PR needs updation concerning the new pf5 upgrade

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 8, 2024
@ibuziuk
Copy link

ibuziuk commented Mar 28, 2024

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 28, 2024
@ibuziuk
Copy link

ibuziuk commented Mar 28, 2024

@jerolimov @sanketpathak @The-Anton could you clarify why the PR is not merged?
also, could you prioritize the recent 4.15 issue related to changes in OpenShift console - #13696

@sanketpathak
Copy link
Contributor

/test e2e-gcp-console

@jerolimov
Copy link
Member

/retest

Signed-off-by: mmusiien <mmusiien@redhat.com>
@musienko-maxim musienko-maxim force-pushed the investigate-flakiness-web-terminal-adminuser branch from b018937 to e6ba1d2 Compare April 23, 2024 11:33
@jerolimov
Copy link
Member

Retry this because #13749 is merged.

/retest

Copy link
Contributor

openshift-ci bot commented Apr 27, 2024

@musienko-maxim: 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 e6ba1d2 link true /test e2e-gcp-console

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/test-infra 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. component/dev-console Related to dev-console jira/valid-bug Indicates that a referenced Jira bug is valid 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.

None yet

8 participants