-
Notifications
You must be signed in to change notification settings - Fork 56
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
e2e: fuzz topology-aware #621
Conversation
Codecov Report
@@ Coverage Diff @@
## master #621 +/- ##
==========================================
+ Coverage 36.27% 39.23% +2.96%
==========================================
Files 52 52
Lines 6388 6943 +555
==========================================
+ Hits 2317 2724 +407
- Misses 3831 3954 +123
- Partials 240 265 +25
Continue to review full report at Codecov.
|
That looks really nice ! I was trying to hack together something very similar using pure bash with random-generated sequence of actions of start, stop, restart, sleep N, fail C, exit C, and check (start/stop/restart the pod, sleep for N, stop container C with a simulated failure/success (exit 1/exit 0), checking actual vs. expected state). Instead of signals I was controlling the containers with a per-pod-per-container hostPath mounted /ctrl/ctrl file system entry which was read with a tail -F loop for commands (exit, fail)... But I'll abort that exercise, this looks so much better, especially I imagine the verification part should be easier. |
0607ee9
to
a053158
Compare
899eef5
to
d134ad8
Compare
|
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
No description provided.