-
Notifications
You must be signed in to change notification settings - Fork 32
Explicitly checking PodPending when reporting Build/Sign status #552
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
Explicitly checking PodPending when reporting Build/Sign status #552
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: yevgeny-shnaidman 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 |
✅ Deploy Preview for kubernetes-sigs-kmm ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/assign @qbarrand |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #552 +/- ##
==========================================
+ Coverage 79.65% 79.69% +0.04%
==========================================
Files 43 43
Lines 4320 4320
==========================================
+ Hits 3441 3443 +2
+ Misses 721 719 -2
Partials 158 158
☔ View full report in Codecov by Sentry. |
/test pull-kernel-module-management-unit-tests |
0fb10ab
to
281a421
Compare
/test pull-kernel-module-management-unit-tests |
281a421
to
bdb2da6
Compare
/test pull-kernel-module-management-unit-tests |
Currently, PodPending phase of a running pod is not explicitly checked, which may cause an unnecessary errors reported. It does not affect the correctness of the flow, but does causes confusion in logs
bdb2da6
to
ade98f9
Compare
/lgtm |
Currently, PodPending phase of a running pod is not explicitly checked, which may cause an unnecessary errors reported. It does not affect the correctness of the flow, but does causes confusion in logs