Skip to content

[AUTO] [main] Add bwc version 2.19.5.#19913

Merged
cwperks merged 1 commit intomainfrom
create-pull-request/patch-main
Nov 14, 2025
Merged

[AUTO] [main] Add bwc version 2.19.5.#19913
cwperks merged 1 commit intomainfrom
create-pull-request/patch-main

Conversation

@opensearch-trigger-bot
Copy link
Copy Markdown
Contributor

I've noticed that a new tag 2.19.4 was pushed, and added a bwc version 2.19.5.

@opensearch-trigger-bot opensearch-trigger-bot bot requested a review from a team as a code owner November 6, 2025 21:46
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Nov 6, 2025

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

@github-actions
Copy link
Copy Markdown
Contributor

❌ Gradle check result for 921679e: 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?

@github-actions
Copy link
Copy Markdown
Contributor

❌ Gradle check result for 921679e: 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?

@github-actions
Copy link
Copy Markdown
Contributor

❌ Gradle check result for 921679e: 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?

@github-actions
Copy link
Copy Markdown
Contributor

❌ Gradle check result for 921679e: 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?

@github-actions
Copy link
Copy Markdown
Contributor

❌ Gradle check result for 921679e: 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?

@andrross andrross force-pushed the create-pull-request/patch-main branch 3 times, most recently from 9077964 to 10611de Compare November 13, 2025 23:36
@andrross
Copy link
Copy Markdown
Member

@cwperks I think the bwc.checkout.align=true option is working against us here. This PR is created before the version update on the 2.19 branch is committed, which means this PR aligns itself to a commit prior to the version change on that branch. We have to rebase this one after the 2.19 version update commit to get things to work...

Signed-off-by: Craig Perkins <craig5008@gmail.com>
Signed-off-by: Andrew Ross <andrross@amazon.com>
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@andrross andrross force-pushed the create-pull-request/patch-main branch from 10611de to 8a047f3 Compare November 14, 2025 01:15
@github-actions
Copy link
Copy Markdown
Contributor

❌ Gradle check result for 8a047f3: 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?

@github-actions
Copy link
Copy Markdown
Contributor

❌ Gradle check result for 8a047f3: TIMEOUT

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?

@github-actions
Copy link
Copy Markdown
Contributor

❌ Gradle check result for 8a047f3: 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?

@github-actions
Copy link
Copy Markdown
Contributor

❕ Gradle check result for 8a047f3: 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.

@codecov
Copy link
Copy Markdown

codecov bot commented Nov 14, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.22%. Comparing base (2fddcd8) to head (8a047f3).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #19913      +/-   ##
============================================
- Coverage     73.25%   73.22%   -0.04%     
+ Complexity    71612    71548      -64     
============================================
  Files          5785     5785              
  Lines        326905   326961      +56     
  Branches      47280    47285       +5     
============================================
- Hits         239480   239417      -63     
- Misses        68220    68324     +104     
- Partials      19205    19220      +15     

☔ 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.

@cwperks cwperks merged commit 7ce0907 into main Nov 14, 2025
36 of 42 checks passed
@andrross andrross deleted the create-pull-request/patch-main branch November 14, 2025 15:04
rgsriram pushed a commit to rgsriram/OpenSearch that referenced this pull request Dec 5, 2025
Signed-off-by: Craig Perkins <craig5008@gmail.com>
Signed-off-by: Andrew Ross <andrross@amazon.com>
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: opensearch-ci-bot <83309141+opensearch-ci-bot@users.noreply.github.com>
liuguoqingfz pushed a commit to liuguoqingfz/OpenSearch that referenced this pull request Dec 15, 2025
Signed-off-by: Craig Perkins <craig5008@gmail.com>
Signed-off-by: Andrew Ross <andrross@amazon.com>
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: opensearch-ci-bot <83309141+opensearch-ci-bot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants