brandon s allbery kf8nh

It was a problem with the older macos GitHub image, which they appear to have fixed last night (my time). This doesn't prove it won't come back at some point...

That's the old image (macos-13), which is used for older ghcs which don't have Apple ARM support (anything before 8.10.5). macos-latest/macos-14 is the new ARM image.

This test has always had sporadic network failures on all platforms. For around a day and a half, though, it was very consistently failing for all jobs using the macos-13...

Well, if it's actually an issue with the image then the right action is to report it to GitHub, but adding a skip for now would avoid a lot of...

That one seems like it might be a little complicated, because it's supposed to have been preferring `--split-sections` for some time now. (Except that that doesn't work on MacOS or...

Manual CI typos(?): * `-fshow-error-context` and `-funoptimized-core-for-interpreter` are missing their leading `f`s * `-fprint-error-index-lists` is actually `-fprint-error-index-links` and requires a parameter

With those corrected, it works here.

Yes. Don't worry about the changelogs failure; that's a GitHub change we're still sorting out, they bumped the version of ghc included in their build images and some of the...

@mergify backport 3.12

> If GHC had a command line mode to create the semaphore and managed them itself then this coupling wouldn't exist. I can't think of any other options immediately. This...