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.x - Refactor writable warm feature flag to include tiering #13799

Merged
merged 1 commit into from
May 27, 2024

Conversation

neetikasinghal
Copy link
Contributor

@neetikasinghal neetikasinghal commented May 23, 2024

Description

Backport #13719

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • API changes companion pull request created.
  • Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
  • Commits are signed per the DCO using --signoff
  • Commit changes are listed out in CHANGELOG.md file (See: Changelog)
  • Public documentation issue/PR created

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.

@neetikasinghal neetikasinghal changed the title 2.x - Refactor writable warm feature flag to include tiering Backport 2.x - Refactor writable warm feature flag to include tiering May 23, 2024
Copy link
Contributor

❌ Gradle check result for 098d92c: 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?

@neetikasinghal
Copy link
Contributor Author

❌ Gradle check result for 098d92c: 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?

#12639

Copy link
Contributor

❌ Gradle check result for 22af0b2: 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?

@neetikasinghal
Copy link
Contributor Author

❌ Gradle check result for 22af0b2: 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?

#13600
#13792
#10193

Copy link
Contributor

❕ Gradle check result for 22af0b2: 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 May 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.40%. Comparing base (0dd892c) to head (22af0b2).
Report is 274 commits behind head on 2.x.

Additional details and impacted files
@@             Coverage Diff              @@
##                2.x   #13799      +/-   ##
============================================
+ Coverage     71.28%   71.40%   +0.11%     
- Complexity    60145    61391    +1246     
============================================
  Files          4957     5037      +80     
  Lines        282799   288378    +5579     
  Branches      41409    42133     +724     
============================================
+ Hits         201591   205905    +4314     
- Misses        64189    65123     +934     
- Partials      17019    17350     +331     

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

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.

2 participants