-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
FreeBSD 13 buildbot is broken #14616
Comments
I think just repointing it at the stable/13 snapshots is probably The Right Thing to do, since it was failing because it tried to grab src.txz from a URL that stopped existing after a week or so. Also enhancing the scripts so they don't eat the error output on failure and so failing to grab src.txz is instantly fatal are probably good ideas. |
13.2 should be released by March 27. |
After thinking about it, I would like to see more branches tested. When the current stable branch is broken, having builds tested against the older stable branch would still be useful because it would warn us about issues like 9fa007d so that we do not merge PRs that break FreeBSD builds. |
13.2-RELEASE has now shipped so it can be used. I am interested in this, how can I help? |
openzfs/zfs-buildbot#272 should fix this. |
This change has been merged and FreeBSD 13.2 builds are working again. |
Are these related?
|
These are a new errors inadvertently introduced by 27a82cb. We should either revert that change or find some reasonable way to handle the warnings on FreeBSD. |
Ah ok, fixed the build bot so it runs, next freebsd can fix the build :) |
I'd added a comment to #14737 (comment) about this. If you have a preferred way to address this please chime in. We're going to want to do something to resolve this fairly promptly. |
I'll have look, I was more worried I had broken it |
PR #14763 was created. If you have any better way addressing this issue, please share. |
Builds are being done against 13.2-beta3, but FreeBSD has removed the tarballs and now have ones for -rc2 on their website. Perhaps we should have builds done against 13.1 instead for the time being.
The text was updated successfully, but these errors were encountered: