← Back to issue list

snapcraft tests leave many ssh defunct processes

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1594876
Type
issue
State
closed
Author
~elopio
Labels
—
Created
Updated
Closed

Current evaluation

Snapcraft tests generated defunct SSH processes. The report was closed without a documented fix, resolution, or linked pull request, indicating the issue was abandoned or resolved internally without tracking.

Suggested action: —

No scores available.

Issue body

$ ps aux | grep ssh jenkins+ 21622 0.0 0.0 0 0 ? Zs Jun15 0:00 [ssh] <defunct> jenkins+ 21623 0.0 0.0 0 0 ? Zs Jun15 0:00 [ssh] <defunct> jenkins+ 22645 0.0 0.0 0 0 ? Zs Jun14 0:00 [ssh] <defunct> jenkins+ 22646 0.0 0.0 0 0 ? Zs Jun14 0:04 [ssh] <defunct> jenkins+ 23596 0.0 0.0 0 0 ? Zs Jun15 0:00 [ssh] <defunct> jenkins+ 23597 0.0 0.0 0 0 ? Zs Jun15 0:04 [ssh] <defunct> jenkins+ 23831 0.0 0.0 0 0 ? Zs Jun13 0:00 [ssh] <defunct> jenkins+ 23832 0.0 0.0 0 0 ? Zs Jun13 0:00 [ssh] <defunct> jenkins+ 24377 0.0 0.0 0 0 ? Zs Jun15 0:00 [ssh] <defunct> jenkins+ 24378 0.0 0.0 0 0 ? Zs Jun15 0:02 [ssh] <defunct> jenkins+ 24824 0.0 0.0 0 0 ? Zs Jun15 0:00 [ssh] <defunct> jenkins+ 24825 0.0 0.0 0 0 ? Zs Jun15 0:00 [ssh] <defunct> jenkins+ 24946 0.0 0.0 0 0 ? Zs Jun15 0:00 [ssh] <defunct> jenkins+ 24947 0.0 0.0 0 0 ? Zs Jun15 0:03 [ssh] <defunct> jenkins+ 28677 0.0 0.0 0 0 ? Zs Jun14 0:00 [ssh] <defunct> jenkins+ 28678 0.0 0.0 0 0 ? Zs Jun14 0:00 [ssh] <defunct> jenkins+ 30864 0.0 0.0 0 0 ? Zs Jun13 0:00 [ssh] <defunct> jenkins+ 30865 0.0 0.0 0 0 ? Zs Jun13 0:00 [ssh] <defunct> jenkins+ 30948 0.0 0.0 11288 932 pts/0 S+ 16:07 0:00 grep --color=auto ssh jenkins+ 31702 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 31703 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 31736 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 31737 0.0 0.0 0 0 ? Zs Jun16 0:05 [ssh] <defunct> jenkins+ 31915 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 31916 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 31947 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 31948 0.0 0.0 0 0 ? Zs Jun16 0:05 [ssh] <defunct> jenkins+ 32087 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 32088 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 32122 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 32123 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 32157 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 32158 0.0 0.0 0 0 ? Zs Jun16 0:03 [ssh] <defunct> jenkins+ 32395 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 32396 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 32435 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 32436 0.0 0.0 0 0 ? Zs Jun16 0:05 [ssh] <defunct> jenkins+ 32612 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 32613 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 32643 0.0 0.0 0 0 ? Zs Jun16 0:00 [ssh] <defunct> jenkins+ 32644 0.0 0.0 0 0 ? Zs Jun16 0:05 [ssh] <defunct> [Impact] * For users, None. * For developers executing the suite locally and for the jenkins slaves, lots of zombie process stay around. [Test Case] * Execute the snapcraft snaps suite and verify that no ssh processes remain. [Regression Potential] * This could make the snaps suite fail, but that would be caught by the PR tests, so we are covered.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b — — Snapcraft tests generated defunct SSH processes. The report was closed without a documented fix, resolution, or linked pull request, indicating the issue was abandoned or resolved internally without tracking.
qwen/qwen3.6-35b-a3b — — Reporting defunct SSH processes left by snapcraft tests, the item was closed without resolution. Ten years of inactivity and zero comments indicate it was abandoned.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The report identified defunct SSH processes left by snapcraft tests, impacting developers and CI runners. No comments or patches were submitted, indicating the issue was abandoned.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1723965 snapcraft doesn't work snapcraft (launchpad) closed Closed without resolution or comments, indicating abandonment. The reported snap command failure and GL driver errors remain unresolved.
72%
#1486659 snapcraft run uses one ssh key to create the image and another to log in snapcraft (launchpad) closed Inconsistent SSH key selection between snapcraft run and ubuntu-device-flash was closed without resolution. Zero comments indicate the report was abandoned or superseded without a fix.
71%
#1898922 snapcraftctl fails, but exit status is zero snapcraft (launchpad) closed Closed without a fix. snapcraftctl incorrectly returned exit status 0 despite npm failures, requiring a manual workaround. The report was abandoned with no comments or resolution.
71%
#4142 snapcraft remote-build exits with return code 0 even when some snaps failed to build for a given arch snapcraft closed Closed without comments or resolution, indicating the request was abandoned. No official fix or merge details were provided.
70%
#1496363 snapcraft fails to build because of missing build-dep for tests snapcraft (launchpad) closed Abandoned. Closed without resolution due to a missing requests build dependency for tests. No comments or follow-up actions were recorded.
70%
#1956216 Snapcraft is no longer working within a Docker container snapcraft (launchpad) closed Closed without resolution. The report detailed a snapcraft ModuleNotFoundError in Docker containers, but received no comments or fixes. The issue remains abandoned.
70%