fix(remotebuild): error early for multiple artifacts per build-on
Metadata
Current evaluation
Merged PR #5005 as commit ad3b54bbd, adding preflight validation to reject remote builds with multiple artifacts on the same build-on architecture; fixes #4995.
Resolution: closed resolved
Reason: PR #5005 was merged as commit ad3b54bbd. It checks the build plan by build-on architecture and emits an informative error before Launchpad can fail obscurely; the PR explicitly fixes #4995 (CRAFT-3279).
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `tox run -m lint`?
- [x] Have you successfully run `tox run -e test-py310`? (supported versions: `py39`, `py310`, `py311`, `py312`)
-----
Launchpad cannot build multiple artifacts on the same build-on architecture and will fail with an esoteric error.
Snapcraft now checks for the scenario and fails with an informative error before the build begins.
Fixes #4995
(CRAFT-3279)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #5005 as commit ad3b54bbd, adding preflight validation to reject remote builds with multiple artifacts on the same build-on architecture; fixes #4995. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #5005 (commit ad3b54bbd) adds early validation for multiple artifacts sharing a build-on architecture, avoiding opaque Launchpad failures and fixing #4995. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged. Adds early validation to prevent Launchpad build failures when multiple artifacts share the same build-on architecture. Replaces cryptic errors with a clear message, resolving issue #4995. Approved and passed CI. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a fix validating remote builds early to prevent esoteric Launchpad failures when multiple artifacts target the same architecture. Snapcraft now exits with a clear error before initiation, resolving issue #4995. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#4995
(confidence 100%)
Issue #4995 reported the unsupported multiple-artifacts-per-build-on scenario fixed by PR #5005.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4995 remote build: error if multiple artefacts can be built on the same architecture | snapcraft | closed | Fixed by merged PR #5005 (commit ad3b54bbd): remote builds now fail early when multiple artifacts share a build-on architecture. | |
| #4495 remote build: odd errors for certain `architectures:` setups | snapcraft | closed | Remote-build architecture handling was improved; #4994 (5cd480725) fixed CLI validation and #5005 (ad3b54bbd) rejected unsupported duplicate build-on artifacts. | |
| #5265 fix(remotebuild): don't fail when cross-compiling | snapcraft | merged | Merged PR #5265 fixed remote cross-compilation by sending build-on architectures to Launchpad; commit f94da8f13 closed #4996. | |
| #4793 fix(remote-build): don't fail with certain archs | snapcraft | merged | Merged into the hotfix branch as commit 53ec55cef, fixing architecture-specific remote-build failures from #4780, with companion support in craft-application#343. |