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

[Backport 2.17] Mute failing status tests from MixedClusterClientYamlTestSuiteIT #15804

Closed
wants to merge 1 commit into from

Conversation

opensearch-trigger-bot[bot]
Copy link
Contributor

Backport 48cf5f0 from #15652.

Signed-off-by: Lakshya Taragi <[email protected]>
(cherry picked from commit 48cf5f0)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Copy link
Contributor

github-actions bot commented Sep 6, 2024

❌ Gradle check result for 775e1c5: 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?

Copy link
Contributor

github-actions bot commented Sep 6, 2024

❌ Gradle check result for 775e1c5: 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?

Copy link
Contributor

github-actions bot commented Sep 6, 2024

❌ Gradle check result for 775e1c5: 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?

@reta
Copy link
Collaborator

reta commented Sep 16, 2024

The 2.17.0 release has sailed away, this change was not included, @sachinpkale please target 2.17.1 if it is still planned for a possible patch release

@sandeshkr419
Copy link
Contributor

@sachinpkale @ltaragi I think we should just close this out if the fix is present in 2.x? Unless absolutely necessary for a future patch release / gradle stability.

Copy link
Contributor

❕ Gradle check result for 775e1c5: UNSTABLE

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 Sep 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.55%. Comparing base (16782e5) to head (775e1c5).
Report is 6 commits behind head on 2.17.

Additional details and impacted files
@@             Coverage Diff              @@
##               2.17   #15804      +/-   ##
============================================
- Coverage     71.56%   71.55%   -0.02%     
+ Complexity    64473    64453      -20     
============================================
  Files          5264     5264              
  Lines        301860   301860              
  Branches      43942    43942              
============================================
- Hits         216038   215993      -45     
- Misses        67744    67846     +102     
+ Partials      18078    18021      -57     

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

@sachinpkale
Copy link
Member

@sachinpkale @ltaragi I think we should just close this out if the fix is present in 2.x? Unless absolutely necessary for a future patch release / gradle stability.

Not required in 2.17, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants