-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS 11.0 running Xcode UI tests is slow, encounters internal errors #2449
Comments
@miketimofeev I am facing the same issue with build. It takes upto 6 hours at time to finish compiling, making github actions unsuitable for ios builds. It is unnecessary waste of time and money. Do you have a work around for this ? |
@vin-fandemand do you mean it takes too much time to compile and run tests in comparison to local build? |
Yes correct. I am using the following configuration, and fastlane to build test and sign the ios application. In local, it takes only upto 15-20mins, while in actions, it takes a long time. I have one running now for almost 2.5 hours.
|
@vin-fandemand the runner VMs are only 3-cores at the moment, which can explain this poor performance. If you believe it's a different problem then please create a separate issue with repro steps so we can take look deeply. |
@miketimofeev is there a way to make the run faster ? Even if there is a premium charge. |
@vin-fandemand, unfortunately, no, at least at the moment. We're continuously working on several improvements, but no ETA for now. |
Description
I am seeing inconsistent bugs and system failures with a GitHub Action that triggers Xcode UI tests on
macOS-11.0
.Area for Triage:
Apple
Question, Bug, or Feature?:
Bug
Virtual environments affected
Expected behavior
Actual behavior
GitHub Actions has encountered an internal error when running your job.
.Repro steps
To reproduce, I select the option to re-run all jobs on this action. Please let me know if you need me to re-run all jobs, happy to do so.
More links
yml for this Action
The text was updated successfully, but these errors were encountered: