openshift
OCPBUGS-14463: Web Terminal e2e tests are failing
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
@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.
@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.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
[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
- ~~OWNERS~~ [jerolimov]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
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
@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 - https://github.com/openshift/console/issues/13696
@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 | e6ba1d29eeef6f198b5e01170c6dcd1deab30952 | 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.