Skip to content

Conversation

@saschagrunert
Copy link
Member

What type of PR is this?

/kind failing-test

What this PR does / why we need it:

This should fix the failing CI
https://github.com/cri-o/cri-o/actions/runs/18988468445/job/54236873693 and let the patch release job work correctly.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

None

@openshift-ci openshift-ci bot added release-note-none Denotes a PR that doesn't merit a release note. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Nov 3, 2025
@saschagrunert saschagrunert changed the title Fix pach-release job by adding dependencies.yaml Fix patch-release job by adding dependencies.yaml Nov 3, 2025
This should fix the failing CI
https://github.com/cri-o/cri-o/actions/runs/18988468445/job/54236873693
and let the patch release job work correctly.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
@openshift-ci openshift-ci bot requested review from klihub and littlejawa November 3, 2025 08:25
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 3, 2025
@saschagrunert saschagrunert force-pushed the release-dependencies-yaml-update branch from 2621866 to 6cbdc99 Compare November 3, 2025 08:25
@saschagrunert saschagrunert added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Nov 3, 2025
@codecov
Copy link

codecov bot commented Nov 3, 2025

Codecov Report

❌ Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 64.31%. Comparing base (7b4dfcf) to head (6cbdc99).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #9544      +/-   ##
==========================================
+ Coverage   64.18%   64.31%   +0.12%     
==========================================
  Files         203      203              
  Lines       28250    28249       -1     
==========================================
+ Hits        18133    18169      +36     
+ Misses       8523     8487      -36     
+ Partials     1594     1593       -1     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@saschagrunert
Copy link
Member Author

/retest

@saschagrunert
Copy link
Member Author

/test e2e-gcp-ovn

@saschagrunert
Copy link
Member Author

@cri-o/cri-o-maintainers PTAL

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-note-none Denotes a PR that doesn't merit a release note.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant