Skip to content

OSD-18645 - Initial implementation for CannotRetrieveUpdatesSRE #404

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

anispate
Copy link
Contributor

@anispate anispate commented Apr 4, 2025

@codecov-commenter
Copy link

codecov-commenter commented Apr 7, 2025

Codecov Report

Attention: Patch coverage is 27.11864% with 43 lines in your changes missing coverage. Please review.

Project coverage is 31.96%. Comparing base (71ed508) to head (503c320).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...nnotretrieveupdatessre/cannotretrieveupdatessre.go 27.11% 42 Missing and 1 partial ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #404      +/-   ##
==========================================
- Coverage   32.08%   31.96%   -0.12%     
==========================================
  Files          35       36       +1     
  Lines        2425     2484      +59     
==========================================
+ Hits          778      794      +16     
- Misses       1587     1629      +42     
- Partials       60       61       +1     
Files with missing lines Coverage Δ
pkg/investigations/registry.go 0.00% <ø> (ø)
...nnotretrieveupdatessre/cannotretrieveupdatessre.go 27.11% <27.11%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@anispate anispate force-pushed the OSD-18645 branch 4 times, most recently from bcb9b3c to f246d1f Compare April 8, 2025 18:17
@anispate anispate force-pushed the OSD-18645 branch 3 times, most recently from c933fc3 to 02d2c44 Compare April 10, 2025 21:11
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 8, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 9, 2025
@anispate anispate force-pushed the OSD-18645 branch 5 times, most recently from ac7a009 to ea1ba08 Compare May 9, 2025 04:09
@anispate anispate changed the title [DRAFT] - OSD-18645 - Initial implementation for CannotRetrieveUpdatesSRE OSD-18645 - Initial implementation for CannotRetrieveUpdatesSRE May 9, 2025
@anispate anispate force-pushed the OSD-18645 branch 4 times, most recently from 74aa572 to 7f8407a Compare May 12, 2025 21:15
@anispate anispate force-pushed the OSD-18645 branch 5 times, most recently from f6ab23c to 0a62198 Compare May 26, 2025 05:22
Copy link
Contributor

openshift-ci bot commented May 27, 2025

@anispate: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@anispate anispate requested a review from typeid May 28, 2025 13:34
@tnierman
Copy link
Member

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 28, 2025
Copy link
Contributor

openshift-ci bot commented May 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anispate, tnierman

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 May 28, 2025
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants