Skip to content

[AUTOCUT] Gradle Check Flaky Test Report for RemoteStoreKafkaIT #17693

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

Closed
opensearch-ci-bot opened this issue Mar 26, 2025 · 3 comments · Fixed by #18216
Closed

[AUTOCUT] Gradle Check Flaky Test Report for RemoteStoreKafkaIT #17693

opensearch-ci-bot opened this issue Mar 26, 2025 · 3 comments · Fixed by #18216
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 26, 2025

Flaky Test Report for RemoteStoreKafkaIT

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

Details

Git Reference Merged Pull Request Build Details Test Name
17289b7 17663 54990 org.opensearch.plugin.kafka.RemoteStoreKafkaIT.testSegmentReplicationWithRemoteStore
4c76c1d 18027 57085 org.opensearch.plugin.kafka.RemoteStoreKafkaIT.testPauseAndResumeIngestion
6b976ea 17836 55861 org.opensearch.plugin.kafka.RemoteStoreKafkaIT.testSegmentReplicationWithRemoteStore
a8b1734 18087 57282 org.opensearch.plugin.kafka.RemoteStoreKafkaIT.testPauseAndResumeIngestion
ddb4354 17893 56370 org.opensearch.plugin.kafka.RemoteStoreKafkaIT.testErrorStrategy
e8b975d 17750 55870 org.opensearch.plugin.kafka.RemoteStoreKafkaIT.testSegmentReplicationWithRemoteStore

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

Catch all triage - 1

@andrross
Copy link
Member

andrross commented May 1, 2025

@yupeng9 @varunbharadwaj Can one of you take a look here? These tests have been pretty flaky. Here's an example:

https://build.ci.opensearch.org/job/gradle-check/57507/consoleText

REPRODUCE WITH: ./gradlew ':plugins:ingestion-kafka:internalClusterTest' --tests "org.opensearch.plugin.kafka.RemoteStoreKafkaIT.testPauseAndResumeIngestion" -Dtests.seed=99C705639E2EC4B4 -Dtests.security.manager=false -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=bem-ZM -Dtests.timezone=SystemV/AST4ADT -Druntime.java=21

RemoteStoreKafkaIT > testPauseAndResumeIngestion FAILED
    java.lang.AssertionError: expected:<2> but was:<4>
        at __randomizedtesting.SeedInfo.seed([99C705639E2EC4B4:473224DAFADE6AA]:0)
        at org.junit.Assert.fail(Assert.java:89)
        at org.junit.Assert.failNotEquals(Assert.java:835)
        at org.junit.Assert.assertEquals(Assert.java:647)
        at org.junit.Assert.assertEquals(Assert.java:633)
        at org.opensearch.plugin.kafka.RemoteStoreKafkaIT.testPauseAndResumeIngestion(RemoteStoreKafkaIT.java:216)

@yupeng9
Copy link
Contributor

yupeng9 commented May 2, 2025

ack, will take a look

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

Successfully merging a pull request may close this issue.

4 participants