Revert "Update Prow to v20210924-1544aef1b6" #3584
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 80fd37d.
google-cla
bot
added
the
cla: yes
istio-testing
added
the
size/M
ericvn
approved these changes
Sep 27, 2021
|
Nevermind, this is confirmed to be a diffeent issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts #3580
The timing of this exactly correlates to istio/istio#35384; see https://testgrid.k8s.io/istio_istio#integ-security-k8s-tests_istio&exclude-non-failed-tests=20&width=20.
Note: it sounds very likely its NOT a prow issue but a GKE issue. However, since this occurred at literally the exact same time as the prow bump, revert seems like a reasonable first step. See kubernetes/test-infra#23741