← Back to issue list

cleanbuild: ensure we enter a shell on failures on --debug

View original Github issue

Metadata

Project
snapcraft
Number
#1404
Type
pull request
State
merged
Author
sergiusens
Labels
Created
Updated
Closed

Current evaluation

Merged to ensure cleanbuild enters a shell on failures when --debug is enabled, regardless of flag positioning. Approved by two reviewers, updating four files with 65 additions and 37 deletions.

Suggested action:

No scores available.

Issue body

No matter how debug was positioned, a shell needs to be entered if a cleanbuild fails. Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com>

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Merged to ensure cleanbuild enters a shell on failures when --debug is enabled, regardless of flag positioning. Approved by two reviewers, updating four files with 65 additions and 37 deletions.
qwen3.6-35b-a3b-mtp-q6 Merged a fix ensuring a shell is entered on cleanbuild failures when --debug is used, regardless of flag positioning. Resolved by maintainer sergiusens.
qwen3.6-35b-a3b-mtp-q6 Merged a fix that ensures a shell is entered upon cleanbuild failure when using --debug, regardless of flag order. This resolves inconsistent debugging behavior during failed builds.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#740 Allow debugging cleanbuild runs. snapcraft merged Merged: Enables debugging for cleanbuild runs by spawning a shell when the --debug flag is used. Approved by reviewers and integrated into the codebase.
82%
#2252 build providers: shell in provider if debug is used snapcraft merged Merged changes enabling shell access in build providers during debug sessions. Approved by a reviewer, passed CI, and updated five files with 112 additions and 21 deletions.
75%
#3718 parts: run debug shell on build environment snapcraft merged Merged. Adds debug, shell, and shell-after flags to launch a build environment shell during parts errors or to replace lifecycle steps. Approved by reviewer, rebased, and passed CI before integration.
72%