Add 2.18.0 version #15712
Add 2.18.0 version #15712
Conversation
reta
requested review from
anasalkouz,
andrross,
ashking94,
Bukhtawar,
CEHENKLE,
dblock,
dbwiddis,
gbbafna,
jainankitk,
kotwanikunal,
linuxpi,
mch2,
msfroh,
nknize,
owaiskazi19,
Rishikesh1159,
sachinpkale,
saratvemulapalli,
shwetathareja,
sohami and
VachaShah
as code owners
|
❌ Gradle check result for 36b344c: 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? |
|
❌ Gradle check result for 36b344c: 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? |
|
Gradle bwc checks are failing without this since 2.17 is already cut, can we merge this for bwc? |
|
@sachinpkale can we merge this?
org.opensearch.index.engine.NRTReplicationEngineTests.testGetSegmentInfosSnapshotPreservesFilesUntilRelease -- flaky test |
|
If there's a flaky test, we need to fix the flaky tests. |
|
❌ Gradle check result for 36b344c: 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? |
|
Closed by mistake, Sorry. |
|
❌ Gradle check result for 36b344c: 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? |
|
❌ Gradle check result for 36b344c: 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? |
|
Flaky: #14012 Which is closed:
Originally posted by @reta in #14012 (comment) |
|
❌ Gradle check result for 36b344c: 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? |
|
❌ Gradle check result for 36b344c: 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? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #15712 +/- ##
============================================
- Coverage 71.95% 71.92% -0.04%
+ Complexity 64192 64185 -7
============================================
Files 5270 5271 +1
Lines 300052 300166 +114
Branches 43368 43380 +12
============================================
- Hits 215917 215898 -19
- Misses 66442 66526 +84
- Partials 17693 17742 +49 ☔ View full report in Codecov by Sentry. |
|
Looks like MacOS builds are stuck. Do you know why @reta? Not sure I understand what's going on. |
|
The MacOS assemble checks should be "fixed" now: #15741 |
Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
Description
Add 2.18.0 version
Related Issues
Needs #15680 first
Check List
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.