fix(remote-build): fail if no artifacts are created
Metadata
Current evaluation
Merged in #4826 (commit 552897340): remote-build now fails when Launchpad creates no artifacts, fixing #4783.
Resolution: closed resolved
Reason: PR #4826 was merged as commit 552897340. It makes remote-build report failure when Launchpad produces no artifacts and resolves #4783.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Fixes #4783
- [ ] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `tox run -m lint`?
- [ ] Have you successfully run `tox run -e test-py310`? (supported versions: `py39`, `py310`, `py311`, `py312`)
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged in #4826 (commit 552897340): remote-build now fails when Launchpad creates no artifacts, fixing #4783. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #4826 (552897340) makes remote-build fail when Launchpad creates no artifacts, fixing #4783. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged fix for issue #4783 that ensures remote builds fail when no artifacts are generated. Approved by two reviewers, passed CI, and merged with 214 additions and 4 deletions across two files. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged by maintainer lengau, this change resolves issue #4783 by ensuring remote builds fail explicitly when no artifacts are generated, preventing silent successes. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#4783
(confidence 100%)
PR #4826 explicitly fixes the reported missing-artifacts failure.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4783 remote build: fail if launchpad fails to create artifacts | snapcraft | closed | Remote-build silently succeeded when Launchpad produced no artifacts. Fixed by merged PR #4826 (commit 552897340), which makes snapcraft remote-build fail when no artifacts are created. | |
| #5080 `snapcraft remote-build` succeeds even if the build fails | snapcraft | closed | Fixed in Snapcraft 8 by PR #4826 (commit 552897340), which makes remote-build fail when Launchpad produces no 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. | |
| #224 fix(remotebuild): create the launchpad instance correctly | craft-application | merged | Merged PR #224 as commit 87bc56a7, fixing remotebuild to create the Launchpad instance correctly. | |
| #3021 remote-build: remove artifact sanity check | snapcraft | merged | Merged PR #3021 (commit e4a878561) removed remote-build's artifact arch sanity check, so Launchpad results with arch 'multi' from build-on are downloaded instead of rejected. Fixes LP bug #1870730. |