craft-platforms errors aren't caught
Metadata
Current evaluation
Closed without a code fix; tracking moved to Jira CRAFT-4371.
Suggested action: —
No scores available.
Issue body
### testcraft.yaml
```yaml
name: testcraft
version: "0.1"
base: ubuntu@24.04
platforms:
a:
build-on: [amd64]
build-for: [all]
b:
build-on: [riscv64]
build-for: [all]
parts:
my-test:
plugin: nil
```
### error
```bash
craft-application/testcraft> python3 __main__.py pack
testcraft internal error: AllSinglePlatformError(message='build-for: all requires exactly one platform definition (2 provided)', details='build-for: all defined in platforms: a,b', resolution="Provide only one platform with only build-for: all or remove 'all' from build-for options.", docs_url=None, doc_slug=None, logpath_report=True, reportable=True, retcode=1)
```
[full pastebin](https://paste.ubuntu.com/p/WHxprfk3Mb/)
### solution
I think that craft-application could either catch and re-raise craft-cli errors or add another `except` block for craft-platforms errors [here](https://github.com/canonical/craft-application/blob/5cf3d4071569e281cf06f07a119e45659d00d3fb/craft_application/application.py#L613).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without a code fix; tracking moved to Jira CRAFT-4371. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a fix. Reported missing exception handling for craft-platforms errors in craft-application. Transferred to Jira ticket CRAFT-4371 for tracking. No code changes or pull requests were merged. | |
| qwen/qwen3.6-35b-a3b | — | — | Reported that craft-platforms validation errors aren't caught by craft-application, causing unhandled internal errors. Suggested adding exception handling. Closed without a public fix or resolution details. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned without a fix; deferred to internal Jira ticket CRAFT-4371. No pull requests were merged to address the uncaught craft-platforms errors. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without a documented fix or merge. The maintainer proposed catching craft-platforms validation errors in craft-application, but no resolution or code changes were implemented. The ticket remains unresolved. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #600 Use platform for build environment names | craft-application | closed | Closed without implementation. Automated Jira syncs indicate tracking moved internally to CRAFT-3859 and CRAFT-3858. No public fix, merge, or resolution was documented, suggesting the request was abandoned or handled offline. | |
| #705 Pack command errors ugly | craft-application | closed | Closed without a fix. Deferred to internal Jira ticket CRAFT-4420. The unhandled RuntimeError for invalid platform builds remains unresolved. |