tests: Update how kube2e tests report and update the glooctl check tests #9634
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
github-actions
bot
added
the
keep pr updated
|
Visit the preview URL for this PR (updated for commit 8de4e7b): https://gloo-edge--pr9634-fix-kube-tests-omit-u37tex6y.web.app (expires Tue, 25 Jun 2024 21:13:33 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 77c2b86e287749579b7ff9cadb81e099042ef677 |
|
https://github.com/solo-io/gloo/actions/runs/9566653960?pr=9637 shows the new reporting structure where multiple failures are shown |
sheidkamp
approved these changes
Jun 18, 2024
jenshu
approved these changes
Jun 19, 2024
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.
Description
XDS pollution occurs with flakey ordering of xds resources as detected in enterprise nack detector for fallback cluster in the case of invalid routes.
This makes enterprise tests fail and can potentially make cluster load assignment appear out of sync until a new update occurs or a pod rolls.
Given that actual impact on production systems is low and the danger of other failing tests not being caught in the interim this is a patch to clean up our test runs.