Repository navigation
ci(pstack): test macOS with its stock bash only, since its runners are scarce - #25
Merged
Merged
Conversation
…e scarce GitHub's macOS arm64 runners are short on capacity, and the macos-latest bash job was cancelled five times in a row without getting a runner, which blocked CI gate on main and on #22. Ubuntu already covers a current bash, and the /bin/bash job still covers bash 3.2 and macOS's stat and date.
mstephenholl
added a commit
that referenced
this pull request
Oct 20, 2026
#27) ## Why #25 cut the macOS install job to one, `/bin/bash`, because the other one kept failing to get a runner. Today the `/bin/bash` job failed the same way three times in a row ("The job was not acquired by Runner of type hosted even after multiple attempts"): once on `main` after #25 merged, and twice on #22. GitHub cancels a job that waits about 15 minutes for a macOS runner. `CI gate` treats a cancelled job as a failure, and the `main` ruleset requires the gate with no bypass, so each shortage blocks every merge and release until a retry gets lucky. ## What changes - **`pstack-ci.yml`**: the install job runs on Ubuntu only. Every job in this file still feeds `CI gate`. - **New `pstack-macos.yml`**: the same install steps on `macos-latest` with `/bin/bash`, on every push to `main`, daily at 06:23 UTC, and on demand. It has no `pull_request` trigger, so it never adds a check to a pull request. A newer commit cancels a run that is still waiting for a runner, so a burst of merges doesn't queue several runs for scarce runners. - **Tests**: `CiWiringTest` now fails if any gated job runs on macOS. The new `MacosWorkflowTest` fixes the triggers, the read-only permissions, and the cancel-on-newer concurrency group, and checks that the macOS steps match the gated Ubuntu install job's steps except for `/bin/bash`. Without that check, the two copies could drift apart now that they live in separate files. - **`port/README.md`**: the CI section describes the new workflow, its trade-off, and how to test a branch on macOS before merging (`gh workflow run pstack-macos.yml --ref <branch>`). ## Risk A bug that shows up only on macOS (bash 3.2, BSD `stat` or `date`) can now merge and ship in a release before its macOS run reports. The run on `main` still catches it within hours, but the fix lands after the release. ## Proof - Each new test fails on the drift it guards against: dropping a step from the macOS job, adding a `pull_request` trigger, and `main`'s current `pstack-ci.yml` with macOS in the gate. - All 248 unit tests pass, `install_test.sh` passes, and `check.py` reports 0 problems. Both workflows parse, with the triggers and runners listed above.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
GitHub's macOS arm64 runners are short on capacity. The
Install (macos-latest, bash)job was cancelled five times in a row today, with the annotation "The job was not acquired by Runner of type hosted even after multiple attempts". That failedCI gateonmain, so #23 never released, and it blocks #22.What changes
The install matrix drops the macOS
bashentry. Ubuntu still tests a current bash. The macOS/bin/bashjob still tests bash 3.2 and macOS'sstatanddate, and it got a runner on every attempt today. Each run now needs one macOS runner instead of two.Risk
A bug that shows up only with a current bash on macOS's userland would go uncaught. Neither of the other two jobs would catch it.
Proof
test_github_settings.pyandcheck.pypass. Merging this releases #23's change too, since the release covers everything since v0.2.14.