Skip to content

Change to use github hosted machines#17

Open
BrunoMazzo wants to merge 6 commits intomainfrom
update-macos-runner
Open

Change to use github hosted machines#17
BrunoMazzo wants to merge 6 commits intomainfrom
update-macos-runner

Conversation

@BrunoMazzo
Copy link
Owner

@BrunoMazzo BrunoMazzo commented Jun 23, 2025

Summary by CodeRabbit

  • Chores
    • Updated iOS testing workflows to use the latest macOS runner environment.
    • Upgraded iOS Simulator version to 18.2 for testing and build processes.
    • Introduced a new continuous integration test target for improved test management.

@coderabbitai
Copy link

coderabbitai bot commented Jun 23, 2025

Walkthrough

The GitHub Actions workflow for iOS testing was updated to run both parallel-testing and single-device-testing jobs on the macos-latest runner instead of self-hosted. Both jobs now use the maxim-lobanov/setup-xcode@v1.6.0 action with the latest stable Xcode. The single-device-testing job test command was changed from make test to make test.ci. The Makefile was updated to add a new test.ci target and to update the iOS Simulator OS version from 18.0 to 18.2 in relevant targets.

Changes

File(s) Change Summary
.github/workflows/ios.yml Changed runner to macos-latest for testing jobs; added Xcode setup step; changed test command to make test.ci
Makefile Added .PHONY target test.ci; updated iOS Simulator OS version from 18.0 to 18.2 in test, test-parallel, and generate-zip targets

Poem

A hop from self-hosted, now GitHub's own,
On macOS-latest, our tests are flown.
Xcode set up fresh, with versions new,
Simulator’s updated, testing through and through.
A new test.ci dance, clean and bright,
Our builds leap forward, swift as light! 🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.github/workflows/ios.yml (2)

11-11: Remove trailing whitespace and verify runner compatibility

YAML lint flags a trailing space on this runs-on line; please remove the extra space. Also confirm that macos-latest provides the required Xcode version and concurrency limits needed for your iOS tests.


44-44: Remove trailing whitespace and verify runner compatibility

YAML lint flags a trailing space on this runs-on line; please remove the extra space. Also ensure that macos-latest meets your Xcode and parallelism requirements for the normal simulator job.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f9d873d and 1ba6bed.

📒 Files selected for processing (1)
  • .github/workflows/ios.yml (2 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/workflows/ios.yml

[error] 11-11: trailing spaces

(trailing-spaces)


[error] 44-44: trailing spaces

(trailing-spaces)

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

♻️ Duplicate comments (1)
makefile (1)

37-37: Duplicate: reuse simulator destination variable.
Same duplication of -destination here—apply the variable defined in the earlier comment.

🧹 Nitpick comments (2)
.github/workflows/ios.yml (1)

47-47: Remove trailing whitespace.
Line 47 has an extra space after macos-latest, which may trigger YAML lint errors.

makefile (1)

52-52: Unify quoting style for -destination flags.
This line uses double quotes while others use single quotes. For consistency, pick one style across all targets.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1ba6bed and 4fb15c3.

📒 Files selected for processing (2)
  • .github/workflows/ios.yml (2 hunks)
  • makefile (2 hunks)
🧰 Additional context used
🪛 actionlint (1.7.7)
.github/workflows/ios.yml

14-14: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


50-50: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 YAMLlint (1.37.1)
.github/workflows/ios.yml

[error] 47-47: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Cloned simulator
  • GitHub Check: Normal simulator
🔇 Additional comments (4)
.github/workflows/ios.yml (4)

11-11: Approve runner switch to hosted macOS.
Changing runs-on to macos-latest aligns with the PR objective to use GitHub-hosted machines.


15-17: Approve Xcode setup step.
Adding maxim-lobanov/setup-xcode@v1.6.0 with latest-stable correctly ensures the workflow uses the desired Xcode version.


51-53: Approve Xcode setup in single-device job.
Mirrors the parallel-testing job and ensures consistency across both workflows.


58-58: Update test command to CI target.
Switching from make test to make test.ci correctly aligns with the new Makefile target.

-scheme Client \
test \
-destination 'platform=iOS Simulator,name=iPhone 16,OS=18.0' \
-destination 'platform=iOS Simulator,name=iPhone 16,OS=18.2' \
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Extract simulator destination string to a variable.
The -destination 'platform=iOS Simulator,name=iPhone 16,OS=18.2' flag is duplicated across targets. Define at the top, e.g.:

SIM_DEST = platform=iOS Simulator,name=iPhone 16,OS=18.2

and then use -destination '$(SIM_DEST)' \.

🤖 Prompt for AI Agents
In the makefile at line 10, the simulator destination string is hardcoded and
duplicated across targets. To fix this, define a variable SIM_DEST at the top of
the makefile with the value platform=iOS Simulator,name=iPhone 16,OS=18.2, then
replace all occurrences of -destination 'platform=iOS Simulator,name=iPhone
16,OS=18.2' with -destination '$(SIM_DEST)' to avoid duplication and improve
maintainability.

Comment on lines +16 to +27
.PHONY: test.ci
test.ci:
$(MAKE) clean-up
$(MAKE) generate-zip
set -o pipefail && xcodebuild -project Client/Client.xcodeproj \
-scheme Client \
test \
-destination 'platform=iOS Simulator,name=iPhone 16,OS=18.2' \
-resultBundlePath test-result.xcresult \
-derivedDataPath 'derivedData' \
-clonedSourcePackagesDirPath SourcePackages \
-disableAutomaticPackageResolution | xcbeautify --report junit
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

DRY up test vs test.ci targets.
Both targets invoke the same xcodebuild command. Consider having test.ci depend on test or extracting shared steps into a helper target to avoid drift.

🤖 Prompt for AI Agents
In the makefile around lines 16 to 27, the test.ci and test targets both run the
same xcodebuild command, causing duplication. Refactor by extracting the common
xcodebuild command into a separate helper target, then have both test and
test.ci depend on that helper. Alternatively, make test.ci depend on test and
only add the extra steps unique to test.ci in its target to avoid code
duplication and ensure consistency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant