-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Try to get more info on TestDevGracefulCancel failures #6662
Conversation
Codecov Report
@@ Coverage Diff @@
## main #6662 +/- ##
==========================================
- Coverage 70.48% 69.99% -0.49%
==========================================
Files 515 522 +7
Lines 23150 23739 +589
==========================================
+ Hits 16317 16616 +299
- Misses 5776 6038 +262
- Partials 1057 1085 +28
Continue to review full report at Codecov.
|
umm. The build passed this time. |
So it looks like the graceful shutdown isn't actually shutting down. |
This panic isn't useful since it's actually the testing instance and not the Skaffold under test. |
Sometimes, I have had to press "Cntrl-C" twice to exit devloop. I always thought it was because I am impatient. |
Adding log statements to better understand what's happening in kokoro. Unfortunately I haven't been able to reproduce the problem locally (on Linux) so far. Related: GoogleContainerTools#6424, GoogleContainerTools#6643, GoogleContainerTools#6662
Debugging the flaky `TestDevGracefulCancel/multi-config-microservices` integration test showed that the kubectl port forwarder was stuck with goroutines waiting on a channels(one per resource). Search for `goroutine 235` and `goroutine 234` in this Kokoro log: https://source.cloud.google.com/results/invocations/a9749ab5-8762-4319-a2be-f67c7440f7a2/targets/skaffold%2Fpresubmit/log This change means that the forwarder also listens for context canceled. **Related**: GoogleContainerTools#6424, GoogleContainerTools#6643, GoogleContainerTools#6662, GoogleContainerTools#6685
Debugging the flaky `TestDevGracefulCancel/multi-config-microservices` integration test showed that the kubectl port forwarder was stuck with goroutines waiting on a channels(one per resource). Search for `goroutine 235` and `goroutine 234` in this Kokoro log: https://source.cloud.google.com/results/invocations/a9749ab5-8762-4319-a2be-f67c7440f7a2/targets/skaffold%2Fpresubmit/log This change means that the forwarder also listens for context canceled. **Related**: #6424, #6643, #6662, #6685
No description provided.