spread: capture developer debug information
Metadata
Current evaluation
Merged PR #2943 (commit 2fe8456b8) enabled developer debug output in spread, improving failure diagnostics without cluttering normal logs.
Resolution: closed resolved
Reason: PR #2943 was merged as commit 2fe8456b8, setting SNAPCRAFT_ENABLE_DEVELOPER_DEBUG=yes in spread so diagnostic output is captured for failed test runs.
Evaluated by: mr-cal-bot
No scores available.
Issue body
This information can often be useful to diagnose what is wrong.
Since spread only spits out the output on failure, it shouldn't
clutter up typical logs.
Sets SNAPCRAFT_ENABLE_DEVELOPER_DEBUG=yes in the spread env.
Signed-off-by: Chris Patterson <chris.patterson@canonical.com>
- [ ] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `./runtests.sh static`?
- [ ] Have you successfully run `./runtests.sh tests/unit`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #2943 (commit 2fe8456b8) enabled developer debug output in spread, improving failure diagnostics without cluttering normal logs. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #2943 set SNAPCRAFT_ENABLE_DEVELOPER_DEBUG=yes for spread, capturing Snapcraft diagnostics on failed runs while keeping normal logs uncluttered. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #2943 (commit 2fe8456b8), enabling developer debug capture in spread so diagnostic output is retained when tests fail. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #2943 sets SNAPCRAFT_ENABLE_DEVELOPER_DEBUG=yes for spread runs, capturing Snapcraft developer diagnostics on failure without cluttering successful-run logs. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged changes setting SNAPCRAFT_ENABLE_DEVELOPER_DEBUG=yes in the spread environment to capture debug logs on failure. Approved by one reviewer, passed CI, and updated four files with twelve added lines. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged changes that set SNAPCRAFT_ENABLE_DEVELOPER_DEBUG=yes in the spread environment. This captures debug information on test failures without cluttering standard logs. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#2976
(confidence 90%)
Merged as 669e936ac; formalized developer debug as a hidden build option and forwarded it into build environments.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5389 test(spread): trace logs in spread tests | snapcraft | merged | Merged PR #5389 as ff6f5950e, adding trace logging to spread tests for better failure diagnostics. | |
| #96 spread: add log output when docker fails to run | rockcraft | closed | Closed unmerged because its Docker-related spread diagnostics were addressed by merged PR #94 in commit ad384842. | |
| #2913 spread: disable journal debug dump unless configured | snapcraft | merged | Merged PR #2913 (commit d444bb248): journal debug dumps now require SPREAD_DEBUG_JOURNAL=true; Travis CI enables them by default. |