-
Notifications
You must be signed in to change notification settings - Fork 2.2k
feat: k8s failure testing #4743
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
Conversation
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.
Let's have an specific file for this specific test
Latency summaryCurrent PR yields:
Breakdown
Backed by latency-tracking. Further commits will update this comment. |
Codecov Report
@@ Coverage Diff @@
## master #4743 +/- ##
==========================================
+ Coverage 87.46% 87.66% +0.20%
==========================================
Files 117 119 +2
Lines 8526 8668 +142
==========================================
+ Hits 7457 7599 +142
Misses 1069 1069
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
make the test required
This adds a more comprehensive test to our K8s based test suite. I separated it so that it runs as its own step and does not prolong the k8s tests even more. This copies a lot of code in ci/cd unfortunately.
The test covers:
Besides the test, I also added retries for failing gRPC requests which are outside our control (non Executor errors etcs).
Closes #4629