release-1.8: Backports for 1.8-rc3#45986
Conversation
(cherry picked from commit 69f10f8)
|
I seem to consistently be getting in the Downloads test with this :/ |
|
But #45408 has been merged 2 months ago on master, it doesn't seem to have been particularly problematic since then. |
|
Well, I see this on both the linux runners that run the Downloads.jl tests and even after a restart. But maybe that endpoint is just down and it is not related to this. |
|
Tests for i686-linux-gnu and win64 are currently failing with the same errors also for #45823, which is totally unrelated. |
|
Closing and reopening doesn't retrigger Buildkite. I contacted support, and they told me that's the intended behavior. To retry a failing Buildkite job, you'll need to go to the Buildkite page and click the retry button for the desired jobs. |
|
Ouch hah! I tried login and it just tells me I am not in the correct github group, or something like that. |
😐 |
In channel iteration and in the `@sync` race check. (cherry picked from commit 4084f7e)
* Update `Documenter` version, deploy to tarball This is a necessary change to get documentation deployed in buildkite, where we deploy first to a tarball, then upload in a separate step. * Update doc/make.jl Co-authored-by: Morten Piibeleht <morten.piibeleht@gmail.com> Co-authored-by: Morten Piibeleht <morten.piibeleht@gmail.com> (cherry picked from commit 43dac09)
|
I'm going to reach out to Buildkite support again to see if they'll reconsider adding the "rebuild when a PR is closed and reopened" feature. |
|
I mean, this is related to the fact they don't build on the merge commit but the tip of the branch. Closing and reopening a PR never changes the tip, you have to actually change that somehow (amend, rebase, whatever) |
(cherry picked from commit 69f10f8)
fixes #45979