I've just set up a new charm recipe for the autocert charm. When requesting a build, the i386 and armhf builds fail. It isn't just a specific series, but for all:
Looking at the build logs, for i386, it's failing on the "charmcraft" snap not supporting this architecture:
"""
error: snap "charmcraft" is not available on stable for this architecture
(i386) but exists on other architectures (amd64, arm64, armhf, ppc64el,
s390x).
"""
"""
Parts processing error: Error installing snap 'charm' from channel 'latest/stable'.
"""
Can we exclude these two architectures by default to avoid the noisy fail to build emails? Also the unnecessary bump in revnos when publishing to the charm store?
Hi,
I've just set up a new charm recipe for the autocert charm. When requesting a build, the i386 and armhf builds fail. It isn't just a specific series, but for all:
kinetic - https:/ /launchpad. net/~autocert- charmers/ autocert- charm/+ charm/autocert/ +build/ 4232/+files/ buildlog_ charm_ubuntu_ kinetic_ i386_autocert_ BU /launchpad. net/~autocert- charmers/ autocert- charm/+ charm/autocert/ +build/ 4209/+files/ buildlog_ charm_ubuntu_ xenial_ i386_autocert_ BUI /launchpad. net/~autocert- charmers/ autocert- charm/+ charm/autocert/ +build/ 4215/+files/ buildlog_ charm_ubuntu_ bionic_ i386_autocert_ BUI /launchpad. net/~autocert- charmers/ autocert- charm/+ charm/autocert/ +build/ 4226/+files/ buildlog_ charm_ubuntu_ jammy_i386_ autocert_ BUIL /launchpad. net/~autocert- charmers/ autocert- charm/+ charm/autocert/ +build/ 4221/+files/ buildlog_ charm_ubuntu_ focal_amd64_ autocert_ BUI
ILDING.txt.gz
xenial - https:/
LDING.txt.gz
bionic - https:/
LDING.txt.gz
jammy - https:/
DING.txt.gz
focal - https:/
LDING.txt.gz
Looking at the build logs, for i386, it's failing on the "charmcraft" snap not supporting this architecture:
"""
error: snap "charmcraft" is not available on stable for this architecture
(i386) but exists on other architectures (amd64, arm64, armhf, ppc64el,
s390x).
"""
For armhf:
xenial - https:/ /launchpad. net/~autocert- charmers/ autocert- charm/+ charm/autocert/ +build/ 4211/+files/ buildlog_ charm_ubuntu_ xenial_ armhf_autocert_ BU /launchpad. net/~autocert- charmers/ autocert- charm/+ charm/autocert/ +build/ 4222/+files/ buildlog_ charm_ubuntu_ focal_armhf_ autocert_ BUI /launchpad. net/~autocert- charmers/ autocert- charm/+ charm/autocert/ +build/ 4228/+files/ buildlog_ charm_ubuntu_ jammy_armhf_ autocert_ BUI /launchpad. net/~autocert- charmers/ autocert- charm/+ charm/autocert/ +build/ 4234/+files/ buildlog_ charm_ubuntu_ kinetic_ armhf_autocert_ B
ILDING.txt.gz
focal - https:/
LDING.txt.gz
jammy - https:/
LDING.txt.gz
kinetic - https:/
UILDING.txt.gz
That's failing because of the "charm" snap:
"""
Parts processing error: Error installing snap 'charm' from channel 'latest/stable'.
"""
Can we exclude these two architectures by default to avoid the noisy fail to build emails? Also the unnecessary bump in revnos when publishing to the charm store?