-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remote build: fails with some architecture definitions #4780
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/CRAFT-2868.
|
I've also seen failures without
(Which works for Miriway, but not for several of canonical's Mir based projects. Not spotted what the significant difference between these is.) |
Also: This works: This does not:
|
snapcraft 2.8.4 appears to have fixed some cases. canonical/mir#3369 builds mir-libs for a matrix of core{22,24}, {amd64,armhf,arm64). The only one failing now is core24,armhf https://github.com/canonical/mir/actions/runs/8939586899/job/24620012565?pr=3369 Running locally, doesn't retrieve any build results to investigate further
|
This fixes the initial reported bug in #4780. However, I haven't tested some other use cases listed in that bug report.
This fixes the initial reported bug in #4780. However, I haven't tested some other use cases listed in that bug report.
This fixes the initial reported bug in #4780. However, I haven't tested some other use cases listed in that bug report. - [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`) -----
Fixes via #4793 and canonical/craft-application#343 |
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
Relevant log output
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)
The text was updated successfully, but these errors were encountered: