Run GitHub Actions workflow on Linux and macOS #26
Conversation
This file contains 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
jansorg
force-pushed
the
jansorg/5.2-github-actions-mac
branch
6 times, most recently
from
c439ecd to
e0016c2
Compare
jansorg
changed the title
jansorg
force-pushed
the
jansorg/5.2-github-actions-mac
branch
from
e0016c2 to
bf6322d
Compare
jansorg
force-pushed
the
jansorg/5.2-github-actions-mac
branch
from
bf6322d to
5587a2e
Compare
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.
This PR extends the GitHub Actions workflow for 5.2 execute on macOS and Linux.
Even though macOS only has bash 3.x by default, AFAIK manu use Homebrew to install and use a recent version Bash.
With this matrix build setup, the CI runtime is still under one minute: https://github.com/rocky/bashdb/actions/runs/9548882962
This PR is not installing pygments because an attempt failed due to excessive runtime. When I debugged this on a local macOS setup via ssh, running bashdb's
osascript -e 'tell application "Terminal" to get the background color of the current settings of the selected tab of front window'did not return unless there was a logged in user session. I'm not able to reproduce this reliably in different sessions and across restarts, though.