remote build: fails with some architecture definitions
Metadata
Current evaluation
Remote build failures with specific architecture definitions or comma-separated --build-for flags were fixed via PR #4793 and craft-application#343.
Suggested action: —
No scores available.
Issue body
### Bug Description
Snapcraft does not handle some definitions of architectures for remote builds and fails immediately with no error or explanation.
It's possible that other variations of `architectures:` will fail too, so we should add a set of regression tests.
### To Reproduce
snapcraft remote-build
### Environment
n/a
### snapcraft.yaml
```shell
name: test-snap
version: '0.1'
summary: test
description: test
grade: devel
confinement: devmode
base: core22
architectures:
- build-on: arm64
parts:
my-part:
plugin: nil
```
### Relevant log output
```shell
All data sent to remote builders will be publicly available. Are you sure you want to continue? [y/N]: y
remote-build is experimental and is subject to change. Use with caution.
Build completed.
Log files:
Artifacts:
```
### Additional context
From @jnsgruk on the snapcrafters channel ([source](https://matrix.to/#/!cniCqhKpzVvOBMHAVt:matrix.org/$XrCuSXWoFQNDYBnro0kQCbS2ffAabd1lwbf4uipS33Y?via=matrix.org&via=ubuntu.com&via=xentonix.net))
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Remote build failures with specific architecture definitions or comma-separated --build-for flags were fixed via PR #4793 and craft-application#343. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed. The remote-build architecture parsing failure was resolved via PR #4793 and craft-application PR #343, which corrected how snapcraft handles architecture definitions and build targets. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved via merged PRs #4793 and craft-application#343, fixing the remote-build failure with specific architecture definitions. The issue is closed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Remote build failures with specific architecture definitions were fixed. The issue was closed after resolution via PR #4793 and craft-application#343, which correctly parse missing build targets and comma-separated architecture lists. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed via PR #4793 and craft-application#343. Snapcraft remote-build now correctly handles architecture definitions and comma-separated targets, resolving the reported silent failures and unsupported architecture errors. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4495 remote build: odd errors for certain `architectures:` setups | snapcraft | closed | Remote build architecture validation errors and misleading logs were fixed via remote-builder improvements and PR 4994. Conflicting build-for flags now yield a user-friendly error, and Launchpad reporting was corrected. Closed. | |
| #4543 fix(remote): parse comma-separated architectures | snapcraft | merged | Merged after approval. Resolves #4516 by enforcing mutual exclusivity between --build-for and --build-on, and adding comma-separated architecture parsing for remote builds. Proceeded despite unrelated spread test failures. | |
| #4990 remote build: Allow comma-separated values for `--build-for` and `--platform` | snapcraft | closed | Fixed via PR #5028. The remote build command now supports comma-separated values for --build-for and --platform, resolving a regression introduced during the migration to craft-application. | |
| #1870730 Architectures keyword incorrectly interpreted by remote-build | snapcraft (launchpad) | closed | Abandoned without a code fix. The remote-build command misinterpreted the architectures keyword, only processing i386 and failing. A CLI workaround using --build-on is recommended instead. | |
| #5028 fix(remotebuild): parse comma-separated architectures | snapcraft | merged | Merged fix for issue #4990 enabling comma-separated architecture parsing for --build-for and --platform remote build arguments. Approved by two reviewers and verified via passing CI and spread tests. |