Summarise what has/has not been completed when failing or entering a `--debug` session
Metadata
Current evaluation
Feature request to print a summary of completed/incomplete build steps when a rockcraft pack fails or when entering a --debug session, to help users understand where they are in the build process. No maintainer response; only an automated Jira sync bot comment. No evidence of implementation in the codebase.
Suggested action: needs triage
Reason: The issue has no labels, no assignee, and the only comment is an automated Jira sync bot message from 2024-02-13. No maintainer has acknowledged, triaged, or responded to the feature request. The last activity was 381 days ago, but the feature (summarizing build step progress on failure or in debug sessions) has not been implemented in the codebase based on the available evidence. This is a legitimate feature request that needs maintainer assessment.
Impact:
40
Quick Win:
18.0
Staleness:
70
Complexity:
55
Confidence:
65
Support Request:
10
Issue body
### What needs to get done
When debugging a failed `rockcraft pack`, as a user it is a challenge to understand what **should** have happened already given how rockcraft parts have multiple steps and can come `after` one another. It would be helpful to a user if a summary was given (or at least accessible somehow, if in a debug session). I think it is probably recreatable if you've enabled detailed logs, but reading that does not feel easily accessible for an average user.
### Why it needs to get done
Debugging is hard already, it does not need to be made harder by used needing to guess where they are in their build process. This would help make engineers more productive
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
18.0
Staleness:
70
Complexity:
55
Confidence:
65
Support Request:
10
|
needs triage | Feature request to print a summary of completed/incomplete build steps when a rockcraft pack fails or when entering a --debug session, to help users understand where they are in the build process. No maintainer response; only an automated Jira sync bot comment. No evidence of implementation in the codebase. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
35
Confidence:
75
Support Request:
5
|
needs triage | Feature request to display a build step summary when rockcraft pack fails or enters debug mode. Unlabelled, inactive for over two years, and awaiting maintainer assessment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
40
Confidence:
80
Support Request:
10
|
close stale | Feature request to display a summary of completed and pending build steps when rockcraft pack fails or enters debug mode. Currently unlabelled, inactive for over two years, and forwarded to an internal Jira ticket. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
45
Confidence:
70
Support Request:
15
|
close stale | Feature request to display a summary of completed and pending build steps when rockcraft pack fails or enters --debug mode. Currently unlabelled, inactive for over two years, and lacks maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
40
Confidence:
75
Support Request:
15
|
needs triage | Show completed and pending build steps when rockcraft pack fails or enters debug mode. Currently requires parsing verbose logs. Internal Jira ticket CRAFT-2495 created. Awaiting triage and assignment. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #556 Have the `--debug` shell inform the user which part and step failed | rockcraft | open | 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. | |
| #421 Show link to full execution logs when `rockcraft pack --debug` enters debug session | rockcraft | open | Feature request: when `rockcraft pack --debug` drops the user into a debug shell after a build failure, also print the full execution log path so the user knows what failed. Maintainer acknowledged the report and explained the outer/inner instance log-copy behavior; no fix has landed. |