ci: reduce gke failures #41018
Merged
ci: reduce gke failures #41018
Conversation
This file contains hidden or 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
|
/ci-gke |
2 similar comments
|
/ci-gke |
|
/ci-gke |
7b70cf1 to
76aa443
Compare
|
/ci-gke |
2 similar comments
|
/ci-gke |
|
/ci-gke |
76aa443 to
c035817
Compare
|
/ci-gke |
1 similar comment
|
/ci-gke |
c035817 to
04fabf3
Compare
|
/ci-gke versions=all |
04fabf3 to
ef97b85
Compare
|
/test |
1 similar comment
|
/test |
This commit changes default GKE test region from us-east1-c to us-west1-c, due to test failure rate being hight. This change reduces the number failures. Signed-off-by: brlbil <birol@cilium.io>
ef97b85 to
465d306
Compare
viktor-kurchenko
approved these changes
Aug 12, 2025
|
/test |
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.
The
conformance-gketests have been failing with the error message:error dialing backend: No agent available,as noted in the opened issue #41037. This PR changes the region, which does not completely solve the problem since the root cause is still unknown. However, after the change, the frequency of the same failure has significantly reduced.Failures have been observed on the main and v1.18 branches, so I have tested the changes on both.
Test runs on the main branch:
Run 16879517490
Run 16882292979
Run 16883759631 (contains an unrelated failure)
Test runs on the v1.18 branch:
Run 16883023090
Run 16884801853 (contains an unrelated failure)
Additionally, there was a scheduled run using the old region that occurred around the same time as the tests above, and the failures were again observed:
Run 16883921129