Closed khaeru closed 7 months ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 98.9%. Comparing base (
707353e
) to head (1945ad0
).
I left a longer discussion above so we can just cite this issue in PRs for the other two repos. Could you please open those?
At some point, we should open a PR (and maybe re-open #473) that updates the install instructions document a minimal work-around, maybe in the “Troubleshooting” section, for users who encounter that issue. As you noted, there are likely to be more in the future. We could then link to that work-around from the other install docs on the stack.
The message_ix "Install from conda-forge" workflow succeeds with macos-latest
, so maybe this offers hints at a solution, too.
@glatterf42 noticed today that CI jobs were failing:
…and traced this to a change in the standard GitHub Actions runners.
macos-latest
now runs on the M1/amd64 architecture.macos-14
=macos-latest
, which is on amd64, or (b)macos-14-large
=macos-latest-large
, which is on x86_64 but (per the above) not free.macos-13
.This PR switches to
macos-13
for these workflows. NB I also had to change the branch protection rule formain
to replacemacos-latest-py3.12
as a required check withmacos-13-py3.12
.macos-12
and eventuallymacos-13
labels will be deprecated and removed by GitHub. The above issue gives 2024-Q3 to deprecate and 2024-Q4 to removemacos-12
, and hasmacos-13
still in general availability ("GA") through 2024-Q4.How to review
Note that the CI checks all pass.
PR checklist