This repository has been archived by the owner on Feb 27, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 34
Flaky CI Tests #251
Comments
If converting an existing Contour to Gateway-API enabled is flaky, maybe doc the API field as immutable. |
xref: #218 could also be the issue. |
Moving to 1.15.0 while the community achieves a consensus on the Gateway API implementation plan. |
Still seeing this in I'll look into this some more and see if I can figure out a fix. May be a matter of adding some retries around updates, or switching to using |
skriss
added a commit
to skriss/contour-operator
that referenced
this issue
Apr 19, 2021
In suite_test.go, wraps Update(...) calls in Eventually(...) to mitigate concurrent modification issues causing test flakes. Closes projectcontour#251. Signed-off-by: Steve Kriss <krisss@vmware.com>
danehans
pushed a commit
that referenced
this issue
Apr 19, 2021
In suite_test.go, wraps Update(...) calls in Eventually(...) to mitigate concurrent modification issues causing test flakes. Closes #251. Signed-off-by: Steve Kriss <krisss@vmware.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
CI jobs are intermittently failing. I'm unable to reproduce the flake, but I believe it's related to updating a Contour from defaults to Gateway-enabled in
test_suite.go
. This issue may be resolved by #250. In the meantime, I suggest disabling this portion of the test since the e2e tests cover Gateway support.xref: #249
The text was updated successfully, but these errors were encountered: