Skip to content
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

cirrus-ci FreeBSD 13.0 builds permafail #5028

Closed
bagder opened this issue Mar 3, 2020 · 6 comments
Closed

cirrus-ci FreeBSD 13.0 builds permafail #5028

bagder opened this issue Mar 3, 2020 · 6 comments
Labels

Comments

@bagder
Copy link
Member

@bagder bagder commented Mar 3, 2020

I did this

CI builds on the freebsd-13-0-snap image results in this error, seemingly permanent:

pkg install -y autoconf automake libtool pkgconf brotli openldap-client heimdal libpsl libmetalink libssh2 openssh-portable libidn2 librtmp libnghttp2 nghttp2 stunnel
Updating FreeBSD repository catalogue...
Fetching meta.txz: . done
Fetching packagesite.txz: .......... done
Processing entries: .......
pkg: wrong architecture: FreeBSD:13.0:amd64 instead of FreeBSD:13:amd64
pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:13.0:amd64
Processing entries... done
Unable to update repository FreeBSD
Error updating repositories!

Exit status: 3

Example

I expected the following

Green builds

@bagder bagder added the build label Mar 3, 2020
@fkorotkov

This comment has been minimized.

Copy link

@fkorotkov fkorotkov commented Mar 3, 2020

I don't think there is anything on our side that we can do about:

pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:13.0:amd64

Cirrus is using images available on Google Cloud Platform (here is a full list). And since you are using 

image_family: freebsd-13-0-snap

to point to the latest available image you might get such unexpected behaviour.

There were already couple of images release in 2020 of FreeBSD 13:

freebsd-13-0-current-amd64-v20200102  freebsd-org-cloud-dev  freebsd-13-0-snap              READY
freebsd-13-0-current-amd64-v20200109  freebsd-org-cloud-dev  freebsd-13-0-snap              READY
freebsd-13-0-current-amd64-v20200116  freebsd-org-cloud-dev  freebsd-13-0-snap              READY
freebsd-13-0-current-amd64-v20200123  freebsd-org-cloud-dev  freebsd-13-0-snap              READY
freebsd-13-0-current-amd64-v20200130  freebsd-org-cloud-dev  freebsd-13-0-snap              READY
freebsd-13-0-current-amd64-v20200206  freebsd-org-cloud-dev  freebsd-13-0-snap              READY
freebsd-13-0-current-amd64-v20200213  freebsd-org-cloud-dev  freebsd-13-0-snap              READY
freebsd-13-0-current-amd64-v20200220  freebsd-org-cloud-dev  freebsd-13-0-snap              READY
freebsd-13-0-current-amd64-v20200227  freebsd-org-cloud-dev  freebsd-13-0-snap              READY

You can try to pin image (instead of using image_family) to pin to a specific version:

image: freebsd-13-0-current-amd64-v20200220

/cc @emaste

@dfandrich

This comment has been minimized.

Copy link
Collaborator

@dfandrich dfandrich commented Mar 3, 2020

@emaste

This comment has been minimized.

Copy link

@emaste emaste commented Mar 3, 2020

TBH breakage like this does surprise me, I'd usually expect more subtle breakage. But yes I think the most expedient fix will be to disable 13.0 for now.

@bagder

This comment has been minimized.

Copy link
Member Author

@bagder bagder commented Mar 3, 2020

Thanks for excellent feedback everyone. So lets disable the FreeBSD 13 builds for now and come back and enable it again in another six months or so.

bagder added a commit that referenced this issue Mar 3, 2020
FreeBSD 13.0 is apparently close to a year away from a stable release
and has proven to cause intermittent builds failures recently.

Assisted-by: Dan Fandrich
Assisted-by: Fedor Korotkov
Fixes #5028
@emaste

This comment has been minimized.

Copy link

@emaste emaste commented Mar 3, 2020

Here's the FreeBSD bug tracking this issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244549

@bagder bagder closed this in 691b71b Mar 4, 2020
@dfandrich

This comment has been minimized.

Copy link
Collaborator

@dfandrich dfandrich commented Mar 12, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

4 participants
You can’t perform that action at this time.