-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
//test/extensions/filters/network/rbac:integration_test flakily times out #35653
Comments
@antoniovleonti it looks like this might be your PR. |
I find this strange because I only made a change to the http filter while it's the network filter test that's timing out. |
Yeah, this should be caused by #33875. |
The timeout flake still exists at head. I don't know if we want to forward fix or revert but I'm going to make a PR to un-revert #35531. |
I reproduced with |
I'm wondering if this can be fixed by just reducing the durations used in that test. I'm testing this now. |
No luck. PTAL @yangminzhu |
#35693) …" (#35655) This reverts commit 7ae5ca5. The flakiness in #35653 is not caused by this PR. If you look at [the failure](https://btx.cloud.google.com/invocations/08f19e64-5934-4ed9-9f4c-e0d14e113360/targets/%2F%2Ftest%2Fextensions%2Ffilters%2Fnetwork%2Frbac:integration_test;config=a48d3689347bfb6aaa2bb9b4c87edaab1bb2d2c4710bec9b6690537c48f15140/log) (you can also find this by going to the issue and clicking the link), the failing test is `RoleBasedAccessControlNetworkFilterIntegrationTest.DelayDenied`. That test was added in #33875 and is still flaky at head. Signed-off-by: antoniovleonti <[email protected]>
The RBAC test seems to be highly flaky, and we've experienced a few failures every day. |
i was just tracking this again as its an ongoing ~frequent flake and also came to the conclusion that this PR is the culprit (apologies @RyanTheOptimist i think i suggested the other previously) im going to raise a revert PR and we can figure out from there |
https://dev.azure.com/cncf/4684fb3d-0389-4e0b-8251-221942316e06/_build/results?buildId=177453&tracking_data=ew0KICAic291cmNlIjogIlNsYWNrUGlwZWxpbmVzQXBwIiwNCiAgInNvdXJjZV9ldmVudF9uYW1lIjogIm1zLnZzcy1waXBlbGluZXMucnVuLXN0YXRlLWNoYW5nZWQtZXZlbnQiDQp9
https://dev.azure.com/cncf/envoy/_build/results?buildId=177474&view=logs&j=4930ecaf-18f4-5b3c-dea3-309729c3b3ae&t=573d8780-d7b9-52e3-b4e0-a89886b0b9ff&l=2823
Yan, can you take a look? Looks like it might be related to #35531
The text was updated successfully, but these errors were encountered: