`test` command provides unhelpful output or failure
Metadata
Current evaluation
`test` still reports only “Testing failed.” for failed spread runs in brief mode; the issue is triaged but lacks a concrete reproduction or expected diagnostic.
Suggested action: keep open
Reason: The current TestingService.run_spread implementation catches CalledProcessError and raises exactly CraftError("Testing failed."), confirming the reported behavior remains. The Triaged and Bug labels support keeping this valid bug open, but placeholder reproduction details and no defined expected output require design and test investigation.
Evaluated by: mr-cal-bot
Impact:
45
Quick Win:
12
Complexity:
48
Confidence:
87
Actionability:
50
Issue body
### Bug Description
If tests failed, in brief mode the `test` command simply says "Testing failed" and provides the execution log.
### To Reproduce
..
### part yaml
```shell
..
```
### Relevant log output
```shell
..
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
12
Complexity:
48
Confidence:
87
Actionability:
50
|
keep open | `test` still reports only “Testing failed.” for failed spread runs in brief mode; the issue is triaged but lacks a concrete reproduction or expected diagnostic. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
10
Complexity:
20
Confidence:
70
Actionability:
40
|
keep open | The `test` command in craft-application shows a generic "Testing failed." error message when tests fail, providing no useful context about what went wrong. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
22
Staleness:
55
Complexity:
45
Confidence:
72
Support Request:
5
|
keep open | test command in brief mode only says 'Testing failed.' on failure. Triaged by maintainer with Jira ticket CRAFT-5058, but no fix committed after 167 days. Code at testing.py:331 still raises bare CraftError('Testing failed.'). | |
| qwen/qwen3.6-35b-a3b |
Staleness:
45
Complexity:
20
Confidence:
70
Support Request:
10
|
keep open | Bug report regarding unhelpful test command output in brief mode when tests fail. Labeled as triaged and a bug, but has seen no maintainer response or activity in 126 days. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
60
Complexity:
20
Confidence:
75
Support Request:
10
|
keep open | Bug report about the test command showing unhelpful output in brief mode when tests fail. Currently triaged but inactive for over three months with no reproduction steps or maintainer follow-up. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/craft-application#757
(confidence 95%)
Commit 7ef53448 previously changed this exact failure-message path, but current HEAD still contains the generic error.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #833 `test` command gives unhelpful error message if extension file is not executable | craft-application | open | The `test` command lacks a preflight executable check for `spread/.extension`, causing allocation retries and a misleading empty-ADDRESS error. |