-
Notifications
You must be signed in to change notification settings - Fork 446
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: odd errors for certain architectures:
setups
#4495
Comments
architectures:
setupsarchitectures:
setups
I just attempted with 7.x and received the following:
Using the below
|
I see 2 things here:
giving strange progress and logs. This line
is certainly misleading. It's a list of all the At the end of the day, Launchpad appears to build the correct snaps but I'm not sure why or how. This will require me to read the Launchpad API more and figure out what architectures we need to parse and pass to it.
gives the error:
I was able to reproduce this on snapcraft 7.x and 8.x. I think it is a duplicate of https://bugs.launchpad.net/snapcraft/+bug/2007789. The problem is that the legacy remote-builder is expecting |
architectures:
setupsarchitectures:
setups
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/CRAFT-3283.
|
We've made many improvements to the remote-builder that shoudl address problems like Launchpad reporting the wrong architectures. Other behaviors here, such as using I'm closing this the main problems here have been addressed or are tracked in a different issue. If anything comes up again, please make a new issue. |
Bug Description
The new
remote-build
method will fail under particular configurations of thearchitectures
section in asnapcraft.yaml
.To Reproduce
Environment
Ubuntu 23.04
snapcraft 8.x (rev. 10143)
snapcraft.yaml
Relevant log output
Logs from three different attempts:
Additional context
Some additional behavior happens in case I expand the
architectures
section to include an additional architecture:Output:
Some extra odd behavior happens if I disable fallback with
SNAPCRAFT_REMOTE_BUILD_STRATEGY=disable-fallback
and expand the architectures stanza as above:Note the repetition of building for
amd64
; especially odd as I don't expect a snap to be built for AMD64 at all given myarchitectures
listed.The two AMD64 build logs indicate that the builds happened on AMD64 machines, with the first log reporting that one snap was successfully built (an ARM64 one), and the second log indicating that two snaps were successfully built (both ARM64 and ARMHF). Both the snap files seem to have all the correct information for being installed on their respective architectures. However, if I had built a non-trivial snap, I'm not convinced they would actually function properly (e.g. AMD64 libs might be inside them).
Setting
force-fallback
instead results in the same error message as I mentioned earlier in this section (as expected).The text was updated successfully, but these errors were encountered: