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

Fix flakiness of RemoteRestoreSnapshotIT.testClusterManagerFailoverDuringSnapshotCreation #17589

Merged
merged 1 commit into from
Mar 19, 2025

Conversation

beanuwave
Copy link
Contributor

Description

The test case org.opensearch.remotestore.RemoteRestoreSnapshotIT.testClusterManagerFailoverDuringSnapshotCreation is flaky.

RemoteRestoreSnapshotIT > testClusterManagerFailoverDuringSnapshotCreation FAILED
    java.lang.NullPointerException: Cannot invoke "org.opensearch.snapshots.SnapshotInfo.snapshotId()" because "snapshotInfo[0]" is null
        at __randomizedtesting.SeedInfo.seed([17FD038E1B5EBC1C:75687A3B8DF56E57]:0)
        at org.opensearch.remotestore.RemoteRestoreSnapshotIT.testClusterManagerFailoverDuringSnapshotCreation(RemoteRestoreSnapshotIT.java:1486)

The test allows snapshot creation to fail and, if it does, verifies that the repository does not include its ID. In this scenario, the snapshot is not created - its snapshot info will be null - which leads to an NPE.

Related Issues

Resolves #14324

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@github-actions github-actions bot added >test-failure Test failure from CI, local build, etc. autocut flaky-test Random test failure that succeeds on second run Storage:Remote labels Mar 14, 2025
Copy link
Contributor

❌ Gradle check result for 31ed84c: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

…ringSnapshotCreation

Signed-off-by: Igonin <[email protected]>
Co-authored-by: Benny Goerzig <[email protected]>
Co-authored-by: Karsten Schnitter <[email protected]>
Co-authored-by: Kai Sternad <[email protected]>
Copy link
Contributor

❕ Gradle check result for ec11e44: UNSTABLE

  • TEST FAILURES:
      1 org.opensearch.index.reindex.UpdateByQueryBasicTests.testMultipleSources

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

Copy link

codecov bot commented Mar 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.49%. Comparing base (e306d51) to head (ec11e44).
Report is 18 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #17589      +/-   ##
============================================
+ Coverage     72.27%   72.49%   +0.21%     
- Complexity    65611    65809     +198     
============================================
  Files          5311     5311              
  Lines        304942   304946       +4     
  Branches      44225    44226       +1     
============================================
+ Hits         220407   221077     +670     
+ Misses        66448    65778     -670     
- Partials      18087    18091       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-project-automation github-project-automation bot moved this to 👀 In review in Storage Project Board Mar 19, 2025
@cwperks cwperks merged commit 007600e into opensearch-project:main Mar 19, 2025
57 checks passed
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Storage Project Board Mar 19, 2025
@cwperks
Copy link
Member

cwperks commented Mar 19, 2025

Thank you for fixing this test!

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 Storage:Remote >test-failure Test failure from CI, local build, etc.
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

[AUTOCUT] Gradle Check Flaky Test Report for RemoteRestoreSnapshotIT
3 participants