-
Notifications
You must be signed in to change notification settings - Fork 1.1k
test: set cri-o systemd restart policy to no #3483
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
test: set cri-o systemd restart policy to no #3483
Conversation
While in production we want cri-o to restart when it crashes, when we're testing we'd like to catch panics and crashes. Set restart policy in the systemd unit file to never restart, so we fail tests that make cri-o panic Signed-off-by: Peter Hunt <[email protected]>
saschagrunert
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
/retest |
Codecov Report
@@ Coverage Diff @@
## master #3483 +/- ##
=======================================
Coverage 44.21% 44.21%
=======================================
Files 100 100
Lines 7681 7681
=======================================
Hits 3396 3396
Misses 3989 3989
Partials 296 296 |
|
/retest |
as they're redundant with make install Signed-off-by: Peter Hunt <[email protected]>
d7572a6 to
856ad18
Compare
|
/retest |
??? |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, mrunalp, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
1 similar comment
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, mrunalp, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@haircommander This is great. Fail fast in CI 👍 |
|
/lgtm |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
While in production we want cri-o to restart when it crashes, when we're testing we'd like to catch panics and crashes. Set restart policy in the systemd unit file to never restart, so we fail tests that make cri-o panic
also drop make install.{systemd,config} when building cri-o, as the targets are already hit when running make install
I consider this a failing test because we are failing to catch when CRI-O crashes
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?