Migrating from Intel to Arm64 macOS Runners
Migrating from Intel runners in most cases involves just changing the type of the runner from macos-13 or macos-latest to any of the FlyCI runner labels.
There are specific situations though, where the workflow needs to be updated as well.
Build fails due to swiftlint errors
Since Mar 18 '24, FlyCI runners have SwiftLint installed by default. No additional steps are needed when migrating from GitHub Intel runners to FlyCI Apple Silicon runners.
If you still experience issues with SwiftLint and other runners, check the troubleshooting guide below.
If you use swiftlint as a code style checker, it might happen to experience errors. This is caused by the fact that the swiftlint library is installed by default in the macos-13 image, but it is not included the macos-XX-arm64 images. Since FlyCI tries to comply with the software installed on the official GitHub images, FlyCI runners as well doesn't have swiftlint installed by default.
Below is the error you might observe:
Exit status of command 'cat ./swiftlint/report.md > /opt/actions-runner/_work/_temp/_runner_file_commands/step_summary_f761ae6f-9d16-4000-9ddf-90d3bae436e0' was 1 instead of 0.
cat: ./swiftlint/report.md: No such file or directory
To fix it, you just need an additional step in your workflow that installs swiftlint:
- name: Install swiftlint
run: brew install swiftlintLibraries are explicitly built for x86_64 architecture
If there are explicit requirements to build libraries for x86_64 architecture or to run tests against such, make sure these are updated accordingly to arm64.
Here are some use cases:
-
If your code is compiled on
x86_64architecture just recompile it onarm64and commit your changes -
In any paths where you look for prebuilt libraries, make sure to change
x86_64in the path toarm64
Review these changes as an example of the abovementioned problems↗.
For any other issues you might experience, feel free to join Discord↗ and post your inquiry there. To leverage FlyCI Professional Support for GitHub Actions, review the additional customer support for GitHub Actions we offer.