← Back to issue list

Have the `--debug` shell inform the user which part and step failed

View original Github issue

Metadata

Project
rockcraft
Number
#556
Type
issue
State
open
Author
sed-i
Labels
—
Created
Updated
Closed
—

Current evaluation

Enhance the --debug failure shell to identify the failed part and lifecycle step; this unlabelled request has only an automated Jira-sync comment and still needs maintainer triage.

Suggested action: needs triage

Reason: The issue has no labels, maintainer response, or prioritization; its only comment is an automated 2024 Jira-sync message. The desired diagnostic improvement and PS1//etc/issue examples are clear, but ownership and exact behavior between Rockcraft and shared Craft Application lifecycle code remain unsettled.

Evaluated by: mr-cal-bot

Impact: 32 Quick Win: 9 Complexity: 42 Confidence: 90 Actionability: 48

Issue body

### What needs to get done When rockcraft takes me into a `--debug` shell, it's not clear what went wrong and I end up poking in `../parts/` to see what's missing and where. It could be handy if the debug shell had a means to inform the user which part and step went wrong, for example: - PS1 envvar - Update and display `/etc/issue` ### Why it needs to get done Quicker troubleshooting.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 32
Quick Win: 9
Complexity: 42
Confidence: 90
Actionability: 48
needs triage Enhance the --debug failure shell to identify the failed part and lifecycle step; this unlabelled request has only an automated Jira-sync comment and still needs maintainer triage.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 17
Complexity: 30
Confidence: 70
Actionability: 80
needs triage Feature request to display the failed part and step name in the --debug shell for quicker troubleshooting. Open, unlabelled, awaiting maintainer assessment.
qwen/qwen3.8-27b
Impact: 40
Quick Win: 24
Staleness: 70
Complexity: 40
Confidence: 60
Support Request: 10
needs triage Feature request: have rockcraft's --debug shell tell the user which part and step failed (e.g. via PS1 or /etc/issue) for quicker troubleshooting. Open, no labels, only a Jira-sync bot comment; no maintainer response or implementation found.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 15
Confidence: 80
Support Request: 10
needs triage Feature request to display the failing part and step in the rockcraft --debug shell prompt or /etc/issue for faster troubleshooting. Currently unlabelled and inactive for over two years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 15
Confidence: 75
Support Request: 0
needs triage Feature request to show the failed part and step in rockcraft's --debug shell. Currently unlabelled with no maintainer response in over two years, awaiting project prioritization.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 15
Confidence: 75
Support Request: 20
needs triage Feature request to display the failing part and step in rockcraft's --debug shell for easier troubleshooting. Currently unlabelled, with a Jira sync comment from April 2024 and no maintainer engagement.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/rockcraft#224 (confidence 95%)

    Rockcraft history records #224 as the change that added --debug support, which this request would augment.

  • Related To: canonical/craft-application#436 (confidence 82%)

    Craft Application later added shared pack-command support for --shell, --shell-after, and --debug, making its lifecycle implementation relevant to scoping this request.

Related issues

No related issues found above the similarity threshold.