← Back to issue list

capture output of `snap` commands

View original Github issue

Metadata

Project
craft-providers
Number
#396
Type
issue
State
closed
Author
mr-cal
Labels
—
Created
Updated
Closed

Current evaluation

Fixed by merged PR #401 (commit d7aa4dc): snap subprocess output is captured and command-failure details are included in SnapInstallationError logs.

Resolution: closed resolved

Reason: PR #401 was merged and added captured stdout/stderr and CalledProcessError details to snap-command failures, resolving the missing diagnostics reported in #396.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### What needs to get done Capture and log stdout and/or stderr of `snap install`, `snap ack`, and other similar commands in https://github.com/canonical/craft-providers/blob/main/craft_providers/actions/snap_installer.py ### Why it needs to get done Sometimes snaps will fail to install. The logs are not helpful because stdout and stderr are not captured. source: - https://github.com/canonical/charmcraft/issues/646 - https://chat.charmhub.io/charmhub/pl/bgi8i75m8fg4jferj3km4ej64a

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Fixed by merged PR #401 (commit d7aa4dc): snap subprocess output is captured and command-failure details are included in SnapInstallationError logs.
qwen/qwen3.6-35b-a3b — closed resolved Fixed in craft-providers#401 by adding logging for snap command stdout/stderr output

Update history

Date Change
created

Related work

Related issues

Issue Project State Summary Similarity
#214 snap installer: capture error details when snap removal fails craft-providers merged Merged PR #214 via commit 12094e8, adding subprocess error details when snap removal fails.
73%