-
Notifications
You must be signed in to change notification settings - Fork 471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TestGlooGatewayEdgeGateway/Tracing/TestSpanNameTransformationsWithoutRouteDecorator #10327
Comments
PR: solo-io#10406 |
Duplicate issue: solo-io#10365 |
With the merging of solo-io#10409, I expect this flake to not longer occur on the main (1.18) branch. There is still an underlying bug that is referenced in the code: #10293. I am marking this issue as closed as I expect the flake to not occur. If we see that this fails on the solo-io/gloo@main branch, then we should re-open this. |
Seeing in 1.17.x. @ashishb-solo @sam-heilbron could you backport if not already done?
|
Which tests failed?
Which tests failed?
Recently added test flaked on its first few nightly runs
https://github.com/solo-io/gloo/actions/runs/11773028593/job/32789301648
The test seems to flake on
TestSpanNameTransformationsWithoutRouteDecorator
only. When we callAssertEventuallyConsistentCurlResponse
, everything runs as expected until we reach this assertion block - then the tests seem to timeout. My suspicion is that the connection timeout is too aggressive (3 seconds).I also added this block to pause the test when the assertion failed:
And ran my own curl requests against the server:
And those requests completed fine, so I'm pretty sure that the cluster is in a good state, and that the timeout is transient.
Initial Investigation
Additional Information
No response
The text was updated successfully, but these errors were encountered: