Closed striezel closed 2 months ago
The one job that failed here was "posix (clang, 14,17, macos-11)". That is a bit strange, because a documentation update should not cause CI failure. Here's what the summary says:
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
That should not happen - unless no such runners are available at all. Turns out they are no longer available: https://github.blog/changelog/2024-05-20-actions-upcoming-changes-to-github-hosted-macos-runners/
In January 2024, GitHub announced the deprecation of macOS 11 and the removal of the runner image by June 2024. The macOS 11 runner image will be removed on 6/28/2024. We recommend updating workflows to use macos-14, macos-13, macos-12, or macos-latest.
We are now past the date when the macOS 11 runner image was removed, and that is why that CI job failed.
Thanks for looking into this and the doc improvements. I don't know much about the CI setup on this project but I think that @mloskot who also contributed to boostorg/boost-ci used it to set it up. So maybe it is just a question of merging with the latest boost-ci (the GH actions part)?
Description
Includes release notes for the changes seen in the table in #748, i.e. the changes for a potential Boost 1.86 release of GIL.
References
See #748.
Tasklist