Skip to content
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

[AUTOCUT] Gradle Check Flaky Test Report for ReactorNetty4StreamingIT #15825

Closed
opensearch-ci-bot opened this issue Sep 6, 2024 · 2 comments
Closed
Assignees
Labels
autocut flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc.

Comments

@opensearch-ci-bot
Copy link
Collaborator

Flaky Test Report for ReactorNetty4StreamingIT

Noticed the ReactorNetty4StreamingIT has some flaky, failing tests that failed during post-merge actions.

Details

Git Reference Merged Pull Request Build Details Test Name
73e14ab 15644 47073 org.opensearch.rest.ReactorNetty4StreamingIT.testStreamingRequestOneBatchBySize
f700f50 15506 45804 org.opensearch.rest.ReactorNetty4StreamingIT.testStreamingRequestOneBatchBySize

The other pull requests, besides those involved in post-merge actions, that contain failing tests with the ReactorNetty4StreamingIT class are:

For more details on the failed tests refer to OpenSearch Gradle Check Metrics dashboard.

@opensearch-ci-bot opensearch-ci-bot added >test-failure Test failure from CI, local build, etc. autocut flaky-test Random test failure that succeeds on second run untriaged labels Sep 6, 2024
@reta reta self-assigned this Sep 30, 2024
@reta reta removed the untriaged label Sep 30, 2024
@reta
Copy link
Collaborator

reta commented Sep 30, 2024

[Catch All Triage - 1, 2, 3, 4]

@reta
Copy link
Collaborator

reta commented Oct 15, 2024

I am closing this one, the last recorded test failure is Sep 2nd (40 days ago)

@reta reta closed this as completed Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autocut flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc.
Projects
None yet
Development

No branches or pull requests

2 participants