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.

Sign up for GitHub

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

Jump to bottom

[AUTOCUT] Gradle Check Flaky Test Report for IngestFromKinesisIT #17678

Open
opensearch-ci-bot opened this issue Mar 25, 2025 · 1 comment
Open

[AUTOCUT] Gradle Check Flaky Test Report for IngestFromKinesisIT #17678

opensearch-ci-bot opened this issue Mar 25, 2025 · 1 comment
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

opensearch-ci-bot commented Mar 25, 2025 •
edited
Loading

Flaky Test Report for IngestFromKinesisIT

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

Details

Git Reference Merged Pull Request Build Details Test Name
29060c6 17667 54943 org.opensearch.plugin.kinesis.IngestFromKinesisIT.testKinesisIngestion_RewindByOffset
3fb09c7 17690 55006 org.opensearch.plugin.kinesis.IngestFromKinesisIT.testKinesisIngestion_RewindByOffset
5c59f30 17615 54933 org.opensearch.plugin.kinesis.IngestFromKinesisIT.testKinesisIngestion_RewindByOffset
b52e63f 17669 54934 org.opensearch.plugin.kinesis.IngestFromKinesisIT.testKinesisIngestion_RewindByOffset

The other pull requests, besides those involved in post-merge actions, that contain failing tests with the IngestFromKinesisIT 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 Mar 25, 2025
@prudhvigodithi
Copy link
Member

prudhvigodithi commented Mar 28, 2025 •
edited
Loading

[Triage]
Thanks @yupeng9 for PR with the fix #17697. we can monitor this AUTOCUT issue and close once we see that there are no PR's impacted by this flaky test and once we see no failures after merge to main.
Thanks
@getsaurabh02 @msfroh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
autocut flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@prudhvigodithi @opensearch-ci-bot