-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add revision-failure test image #14875
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #14875 +/- ##
==========================================
- Coverage 85.79% 85.77% -0.03%
==========================================
Files 198 198
Lines 15126 15153 +27
==========================================
+ Hits 12978 12997 +19
- Misses 1826 1830 +4
- Partials 322 326 +4 ☔ View full report in Codecov by Sentry. |
/retest |
/retest |
Are we planning to re-use it in tests? |
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.
/hold other than the two nits, LGTM. Feel free to either update or just unhold
/lgtm
/approve
/assign @izabelacg |
/LGTM |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso, izabelacg, ReToCode 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 |
/hold cancel |
/test istio-latest-no-mesh |
/retest |
This let's you control which revisions fail on startup by updating a config map with the revision name as the key
eg.
kubectl patch configmap revision-failure -p '{"data":{"revision-failure-00001":"1"}}'
This is useful for debugging so thought it would be worth contributing