Skip to content

Conversation

@kh3ra
Copy link
Contributor

@kh3ra kh3ra commented Nov 3, 2025

Description

[Describe what this change achieves]

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

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.

@kh3ra kh3ra changed the title test fix merge-scheduler-config-test-fix Nov 3, 2025
Signed-off-by: Aditya Khera <kheraadi@amazon.com>
@kh3ra kh3ra force-pushed the dev/merge-scheduler-config-test-fix branch from f0d143b to 6f70231 Compare November 3, 2025 07:40
@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2025

✅ Gradle check result for 6f70231: SUCCESS

@codecov
Copy link

codecov bot commented Nov 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.17%. Comparing base (d822f62) to head (6f70231).

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #19870      +/-   ##
============================================
+ Coverage     73.09%   73.17%   +0.07%     
- Complexity    71060    71135      +75     
============================================
  Files          5754     5754              
  Lines        325230   325230              
  Branches      47035    47035              
============================================
+ Hits         237735   237992     +257     
+ Misses        68359    68137     -222     
+ Partials      19136    19101      -35     

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

Signed-off-by: Aditya Khera <kheraadi@amazon.com>
@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2025

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

Signed-off-by: Aditya Khera <kheraadi@amazon.com>
@github-actions
Copy link
Contributor

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

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

@kh3ra kh3ra force-pushed the dev/merge-scheduler-config-test-fix branch from 728a051 to 8419a87 Compare November 25, 2025 15:56
@github-actions
Copy link
Contributor

❌ Gradle check result for 8419a87: null

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

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant