[IGNORE] - Tests to validate GCP e2e tests failures [release-4.15]#1012
[IGNORE] - Tests to validate GCP e2e tests failures [release-4.15]#1012camilamacedo86 wants to merge 1 commit into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: camilamacedo86 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/retest-required |
|
/test e2e-gcp-console-olm |
|
/test e2e-gcp-olm |
|
GCP tests are in perma-fail. |
|
/retest-required |
|
/test e2e-gcp-console-olm |
|
/test e2e-gcp-olm-flaky |
|
/test e2e-gcp-olm |
|
/test e2e-gcp-console-olm |
|
/test e2e-gcp-olm |
2 similar comments
|
/test e2e-gcp-olm |
|
/test e2e-gcp-olm |
|
@camilamacedo86: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
I pulled up a clusterbot with this PR (I guess I could have just used 4.15 XDD) and ran the e2e tests individually against that cluster: |
|
Hi @perdasilva It seems like a very odd flake. |
it is - and I think it shows up a bit T_T maybe we could carve out some time from an upcoming sprint to investigate |
|
Fixed =DD |
|
/close |
|
@perdasilva: Closed this PR. DetailsIn response to this:
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. |
No description provided.