Bad error message if 'spread.yaml' is missing
Metadata
Current evaluation
Closed without resolution. A missing spread.yaml caused an internal error during crafttool test. No fix was implemented or merged. The ticket was closed after a Jira sync comment, indicating it was abandoned.
Suggested action: —
No scores available.
Issue body
### Bug Description
When running the 'test' command, we get an internal error if `spread.yaml` is missing.
### To Reproduce
Run `crafttool test` on a directory that has a valid project but no `spread.yaml`
### part yaml
```shell
```
### Relevant log output
```shell
n/a
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. A missing spread.yaml caused an internal error during crafttool test. No fix was implemented or merged. The ticket was closed after a Jira sync comment, indicating it was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The issue reported an internal error when crafttool test runs without spread.yaml. No fix or discussion occurred, only an automated Jira sync notification. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and closed without a documented fix. The reported internal error when spread.yaml is missing during crafttool test remains unaddressed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without a fix. Reported as an internal error when running crafttool test without spread.yaml, the issue was synced to Jira and closed after minimal activity, indicating it was abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #697 `test` command fails with a FileNotFoundError if `spread` is not on `$PATH` | craft-application | closed | Closed without a documented fix. A bot comment indicates the bug was synced to external Jira ticket CRAFT-4373 for tracking, suggesting the issue was deferred or handled outside GitHub. | |
| #698 Some valid `spread.yaml` files don't get parsed correctly. | craft-application | open | Bug report that some valid spread.yaml files accepted by spread fail to parse in craft's test command, e.g. a backend systems list containing a plain string like 'ubuntu-18.04-64'. No maintainer response or labels; only an auto Jira-sync bot comment. Likely already fixed by PR #737 (accept string system models). |