-
Notifications
You must be signed in to change notification settings - Fork 449
make go routines shutdown gracefully #2784
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
c888206
to
1ea0283
Compare
There's still one last leak, this time in the libbpfgo. @rafaeldtinoco WDYT?
|
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, your call if you want to merge before fixing the libbpfgo one or commit the bump for that on top. 8000 p>
1ea0283
to
13c48ff
Compare
Let's merge it. I'll raise a libbpfgo issue to be tackled in the future. |
Please rebase to HEAD before trying tests again. The rate limit issue with docker hub has been fixed. |
13c48ff
to
26b9f8c
Compare
Working on it. |
Sorry for the noise, we were reaching docker hub rate limits and I tried something that did not work. Could you please rebase and try the tests again ? Thanks! |
26b9f8c
to
4713b24
Compare
4713b24
to
85d9ffe
Compare
1. Explain what the PR does
Fixes: #2763
2. Explain how to test it
One can detect the go routine leakage running
sudo make test-integration
with the help of goleak.3. Other comments