podman system service: takes 4-6s to clean up on interrupt #11921
Assignees
Labels
flakes
Flakes from Continuous Integration
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
rootless
Comments
|
@jwhonce PTAL |
|
@edsantiago While in server.go for the pprof work, I "fixed" the issue where the API service was not shutdown in an orderly manner when --time=0. At the given logging level for these tests, I cannot determine if they were spurious but I will try to recreate on my laptop. |
jwhonce
added
the
In Progress
|
...and, another one. I get the feeling this might soon become our number-one flake. |
edsantiago
changed the title
jwhonce
added a commit
to jwhonce/podman
that referenced
this issue
Oct 12, 2021
* Increase timeout for tests to 10s * To aid in debugging add PID to shutdown package logging * Added new message for forced service shutdown * Always wait for HTTP server to shutdown, duration of 0 not friendly to clients Note: The log event "IdleTracker: StateClosed transition by connection marked un-managed" denotes a TCP connection has been initiated but no HTTP request was sent. And is expected during these tests. Fixes containers#11921 Signed-off-by: Jhon Honce <[email protected]>
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
New flake. It's a one-off, but ISTR something new last week dealing with pprof, so am filing with just one single data point:
podman system service verify pprof endpoints [It] are available
podman system service verify pprof endpoints [It] are not available
(all links are to the same log, same run).
(Tagging as
rootlessbut that may just be serendipity. I will remove the tag if I see a failed root run).The text was updated successfully, but these errors were encountered: