-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Update BinaryBuilder libuv to 2.0.1+4 #41900
Conversation
Sounds good to me. Probably good to have Elliot sign off on this as well before merging. |
Not sure how to do this with Buildbot, but when we switch to Buildkite, we can condition the flag based on which branch is being built (master, release-1.6, release-1.7, etc.). |
The FreeBSD CI failure is
which I've not observed locally. |
Also Julia now builds successfully on FreeBSD 13 without setting |
5d88a9d
to
c1e855d
Compare
Rebased to see whether that fixes anything, since I can't reproduce. |
The buildkite stuff is failing with
|
I restarted the FreeBSD buildbots and the build passed successfully. I don't expect the tests to pass at the moment (for reasons unrelated to this PR). |
The FreeBSD binaries for this build are built with FreeBSD 12 rather than FreeBSD 11, which will work around issue 34627.
c1e855d
to
051ccf9
Compare
Summary of CI failures, all of which appear unrelated to this PR:
|
The FreeBSD binaries for this build are built with FreeBSD 12 rather than FreeBSD 11, which will work around issue JuliaLang#34627.
The FreeBSD binaries for this build are built with FreeBSD 12 rather than FreeBSD 11, which will work around issue JuliaLang#34627.
The FreeBSD binaries for this build are built with FreeBSD 12 rather than FreeBSD 11, which will work around #34627 now that support for FreeBSD 11 has been officially discontinued. Before closing that issue I'd like to verify whether binaries built for FreeBSD 12 will work on 13 so that I don't have a copy-paste a new issue with 11 and 12 incremented to 12 and 13. 😄
Note that the FreeBSD buildbot won't notice this change since we have it set to build with
USE_BINARYBUILDER_LIBUV=0
specifically to work around #34627. Once this is merged, it would be nice if we could figure out a way to conditionally set that flag.