Show link to full execution logs when `rockcraft pack --debug` enters debug session
Metadata
Current evaluation
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.
Suggested action: needs triage
Reason: The issue has no labels or assignee and the only maintainer interaction is tigarmo's Nov 2023 explanation of the two-instance log architecture, with no acknowledgement that the request itself is valid or planned. The 1.15 release notes mention printing the error before opening the debug shell, which partially addresses the UX gap, but there is no evidence the full-log link is now shown, so the issue remains untriaged and possibly partially addressed.
Impact:
30
Quick Win:
19.5
Staleness:
70
Complexity:
35
Confidence:
60
Support Request:
10
Issue body
### What needs to get done
When `rockcraft pack --debug` exits in error, provide the user with the link to the full execution log before landing the user in the debug session.
### Why it needs to get done
The current state looks like this:
```
rockcraft pack --debug
'override-prime' in part 'backend' failed with code 1.
Launching shell on build environment...
root@rockcraft-katib-ui-on-amd64-for-amd64-19746510:~/project#
```
The user has no context as to what happened. If they then type `exit` and complete the rockcraft session, they're provided with:
```
2023-11-28 09:13:41.104 Full execution log: '/home/scribs/.local/state/rockcraft/log/rockcraft-20231128-091052.127801.log'
```
This log would be convenient to have when they hit the debug session. Otherwise they don't know what they're debugging, and the logical solution is to run the command once, `exit`, read the log, then relaunch the debug session
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
19.5
Staleness:
70
Complexity:
35
Confidence:
60
Support Request:
10
|
needs triage | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
10
Confidence:
90
Support Request:
0
|
keep open | Request to print the full execution log path before entering the debug session when rockcraft pack --debug fails. Maintainer acknowledged the UX gap and explained the outer/inner process architecture, but no fix has been implemented in over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
75
Support Request:
10
|
needs triage | Feature request to display the full execution log path immediately when rockcraft pack --debug fails and drops into a debug shell. Currently unlabelled and awaiting prioritization. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
82
Complexity:
15
Confidence:
85
Support Request:
10
|
keep open | Feature request to display the full execution log path when rockcraft pack --debug fails and drops into a shell. A maintainer acknowledged the UX gap and explained the sandbox architecture, but the improvement remains unimplemented after nearly three years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
30
Confidence:
65
Support Request:
10
|
needs triage | Print the full execution log path immediately when rockcraft pack --debug enters a debug session after a failure. Currently, users only see it after exiting, complicating debugging. The improvement is acknowledged and pending implementation. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #483 Summarise what has/has not been completed when failing or entering a `--debug` session | rockcraft | open | 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. |