Skip to content

Conversation

@opensearch-trigger-bot
Copy link
Contributor

I've noticed that a new tag 2.18.0 was pushed, and incremented the version from 2.18.0 to 2.18.1.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2024

❌ Gradle check result for 5ffb171: 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
Contributor

github-actions bot commented Nov 6, 2024

❌ Gradle check result for f20bf94: 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
Contributor

github-actions bot commented Nov 6, 2024

❌ Gradle check result for f20bf94: ABORTED

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
Contributor

github-actions bot commented Nov 6, 2024

❌ Gradle check result for f20bf94: 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
Contributor

github-actions bot commented Nov 6, 2024

❌ Gradle check result for f20bf94: 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
Contributor

github-actions bot commented Nov 6, 2024

❌ Gradle check result for f20bf94: 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
Contributor

reta commented Nov 6, 2024

The test case is not flaky and fails consistently, filed #16580

@github-actions
Copy link
Contributor

github-actions bot commented Nov 6, 2024

❌ Gradle check result for f20bf94: 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
Contributor

github-actions bot commented Nov 6, 2024

❌ Gradle check result for f20bf94: 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
Contributor

github-actions bot commented Nov 7, 2024

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

@reta reta force-pushed the create-pull-request/patch-2.18 branch 3 times, most recently from 1be1a8c to c0143f9 Compare November 7, 2024 21:12
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Update Version.java

Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
@reta reta force-pushed the create-pull-request/patch-2.18 branch from c0143f9 to 4fd6ccd Compare November 7, 2024 21:14
@github-actions
Copy link
Contributor

github-actions bot commented Nov 7, 2024

❌ Gradle check result for 4fd6ccd: 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
Contributor

github-actions bot commented Nov 7, 2024

❌ Gradle check result for 4fd6ccd: 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
Contributor

github-actions bot commented Nov 8, 2024

✅ Gradle check result for 4fd6ccd: SUCCESS

@codecov
Copy link

codecov bot commented Nov 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (2.18@1c157dc). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             2.18   #16571   +/-   ##
=======================================
  Coverage        ?   71.85%           
  Complexity      ?    65339           
=======================================
  Files           ?     5312           
  Lines           ?   304996           
  Branches        ?    44440           
=======================================
  Hits            ?   219141           
  Misses          ?    67537           
  Partials        ?    18318           

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

@dbwiddis dbwiddis merged commit 1ddb631 into 2.18 Nov 8, 2024
39 checks passed
@dbwiddis dbwiddis deleted the create-pull-request/patch-2.18 branch November 8, 2024 01:03
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