-
Notifications
You must be signed in to change notification settings - Fork 2k
[AUTOCUT] Gradle Check Flaky Test Report for ReactorNetty4StreamingStressIT #15840
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
Comments
Closing, the test suite timeout:
|
@reta Unfortunately this failed again on PR #18060 which did contain the change from #18008:
|
Got it, thanks @andrross , I will take a look shortly, sorry about that |
I spent a few minutes looking into this, but couldn't figure out a fix. This is the relevant code: Lines 69 to 80 in 473665f
When it fails it seems to match the first "onNext" match, then it closes the client (which takes 5 seconds due to the graceful shutdown of the backing executor), then it advances the time on the scheduler, but then it never receives the expected error. It will then time out after 10 seconds and fail the test. |
Yeah, the logic seems to be sound but still not stable - I will be looking, sorry it is taking a bit longer |
@reta I had trouble reproducing this, but I can get it to fail in the same way by changing the client close call to be |
New failure here: https://build.ci.opensearch.org/job/gradle-check/58016/
|
Thanks @andrross , looking into it |
Flaky Test Report for
ReactorNetty4StreamingStressIT
Noticed the
ReactorNetty4StreamingStressIT
has some flaky, failing tests that failed during post-merge actions.Details
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.classMethod
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
org.opensearch.rest.ReactorNetty4StreamingStressIT.testCloseClientStreamingRequest
The other pull requests, besides those involved in post-merge actions, that contain failing tests with the
ReactorNetty4StreamingStressIT
class are:For more details on the failed tests refer to OpenSearch Gradle Check Metrics dashboard.
The text was updated successfully, but these errors were encountered: