@erkki-lukk We won’t be including Rosetta in our images, especially as Xcode is no longer supported under Rosetta (see release notes for more details).
However, you can look at the macOS orb example for how to install it for your jobs.
1 Like
Thanks @alexazl !
Looks like we are able to get a M1 resource allocated. However our MacOS jobs seem to be hanging (only on the M1 infrastructure) when running our iOS app test pipeline with the following error
[02:01:42]: ▸ 2023-04-21 02:01:42.292 xcodebuild[7452:37558] IDETestOperationsObserverDebug: Failure collecting logarchive: Error Domain=NSCocoaErrorDomain Code=516 "“test-session-systemlogs-2023.04.21_01-59-28-+0000.logarchive” couldn’t be moved to “My Mac_0000FE00-57B084FD5CA7035B” because an item with the same name already exists." UserInfo={NSSourceFilePathErrorKey=/var/tmp/test-session-systemlogs-2023.04.21_01-59-28-+0000.logarchive, NSUserStringVariant=(
[02:01:42]: ▸ Move
[02:01:42]: ▸ ), NSDestinationFilePath=/Users/distiller/Library/Developer/Xcode/DerivedData/Snapsell-ejlqvjdvyflqffcprmkavavazfey/Logs/Test/Run-*********-2023.04.21_01-50-26-+0000.xcresult/Staging/2_Test/Diagnostics/My Mac_0000FE00-57B084FD5CA7035B/test-session-systemlogs-2023.04.21_01-59-28-+0000.logarchive, NSFilePath=/var/tmp/test-session-systemlogs-2023.04.21_01-59-28-+0000.logarchive, NSUnderlyingError=0x60000321d590 {Error Domain=NSPOSIXErrorDomain Code=17 "File exists"}}
Are you aware of this issue?
I got the same issue. So am I able to build on M1 if using a performance monthly plan?
I can confirm that it runs on M1 now, with macos.m1.large.gen1
1 Like
I had my team look at this and it appears to a bug in Xcode that’s trying to write a log file that already exists. I did find this Stack Overflow from a month ago, which suggests disabling the parallel testing option in Xcode. Please try that and let me know if it resolves your issue. Thank you!
Great! Thank you for the confirmation!!
Yes, customers on performance monthly plans are able to use M1 now! As I mentioned above, that issue appears to be a bug in Xcode. Please try disabling the parallel testing option in Xcode (as suggested on Stack Overflow).
@alexazl Thanks for sharing. On checking, we don’t have Xcode test parallelisation option enabled on any of our targets. So I am not sure why this behavior could be affecting our test target execution.
Also puzzled as this never happens on any of our execution on Intel Mac resources but only on Apple silicon resources.
I am confirmed, it’s working now. If you your target is not have test, or the option is disable already. So you would need do nothing. Just change
resource_class to macos.m1.large.gen1
Thanks @alexazl
Job was rejected because resource class macos.m1.large.gen1, image xcode:14.3.0 is not a valid resource class
Seems Xcode 14.3 is not supported on macos.m1.large.gen1. Any idea when that will be available?
2 Likes
We expect to have Xcode 14.3 available on M1 in the next couple weeks. We’ll announce it here when available, but you can also check our docs for the latest supported images.
2 Likes
Might I ask why such a long wait for Xcode 14.3? It’s been available on Intel for 3 weeks. Do we expect that every release of Xcode on M1 will have a similar lag time?
I’m asking because I’m a huge fan of the M1 performance gains I’ve received so far (decreased build times by over 50%!) so I’m a little concerned about this.
Apologies for the delays in getting these images out. Our image automation and distribution process needed some significant updates for the new Apple silicon architecture and it proved more challenging than we hoped. However, we’ve finished that work and will be releasing the rest of the M1-supported images early next week!
Moving forward, new images will be released to Intel and Apple silicon at roughly the same time.
3 Likes
We are excited to announce that the the remaining Apple silicon images are now available! Below are the software manifests for each supported image:
Happy building!!
3 Likes
I haven’t heard any other reports, but did have my team look into it. Unfortunately, it does appear to be a bug with Xcode and not something that we can mitigate. If the parallelism setting fix didn’t pertain to your situation, though, I recommend reaching out to the Xcode community to see if there’s another way to resolve the issue.
Will do! Thank you!
I have one more issue with the macos.M1 runner - the app is generating a swift file from gql files, using apollos codegen as a run script.
This worked fine on intel runner but fails as the file then cant be found.
It seems that ${PROJECT_DIR} points to a wrong destination: /Users/distiller/project/
Has anyone had similar isssue? Is there a fix?
I am wondering why do I have the following error:
image xcode:13.4.1 is not a valid resource clas
According to the docs its still should be supported:
@MikePendo Please open a support ticket and include links to the build with that error. We’d be happy to dig deeper into the issue for you!