Explicitly specify the Catalina operating system version and update the default Xcode version in the test suite Workflow #18373
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.
Summary
While the
macos-latest
GitHub Actions workflow label still is a valid reference for themacOS Catalina 10.15
virtual environment, with the advent ofmacOS Big Sur 11.x
macos-latest
may be a confusing label to use.It might be clearer to simply use the explicit workflow label containing the major + minor version.
Additionally, this PR updates the job name, as the latest default Xcode version to ship with the
macos-10.15
environment is actually12.0.1
(and not11
as the job name would suggest).See: actions/runner-images#2056 and https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xcode
Issues When Attempting To Add Big Sur Job
As part of the changes in this PR, I wanted to also add some tests for Big Sur but failed to complete this task with a passing build.
What I found was interesting (and I could definitely be doing something incorrectly).
It is interesting to note that the the default Xcode version for the
macos-11.0
GitHub Actions workflow label is11.7
.Attempt adding
macos-11.0
job without setting Xcode to12.2
explicitlyWhen the job using Big Sur with the default Xcode version runs its configuration step, I see the following errors
Additional data:
macos-11.0
environment has a default Xcode version of11.7
by looking at the output ofxcodebuild -version
for this failed configuration stepAttempt adding
macos-11.0
job after setting Xcode to12.2
explicitlyAfter
sudo xcode select
-ing/Applications/Xcode_12.2.app
, the configuration step runs successfully, but I see a test failureAdditional data:
Hopefully this section on investigating trying to add a job for Big Sur makes sense and is at least somewhat coherent. I could very well be doing something incorrectly but was hoping to get some feedback on what that "something" is, if possible.