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
Comments
I don't think there is anything on our side that we can do about:
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: freebsd-13-0-current-amd64-v20200220 /cc @emaste |
13.0 is still probably close to a year away from a stable release, so such
breakages don't surprise me much. We could also just remove 13.0 for now and
add it back once it works again.
|
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. |
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. |
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
Here's the FreeBSD bug tracking this issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244549 |
FWIW, the FreeBSD 13.0 image seems to be working again.
|
I did this
CI builds on the freebsd-13-0-snap image results in this error, seemingly permanent:
Example
I expected the following
Green builds
The text was updated successfully, but these errors were encountered: