Skip to content
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

Closed
1 of 7 tasks
kyle-n opened this issue Jan 14, 2021 · 7 comments
Closed
1 of 7 tasks

macOS 11.0 running Xcode UI tests is slow, encounters internal errors #2449

kyle-n opened this issue Jan 14, 2021 · 7 comments
Labels
Area: Apple bug Something isn't working OS: macOS

Comments

@kyle-n
Copy link

kyle-n commented Jan 14, 2021

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

  • Ubuntu 16.04
  • Ubuntu 18.04
  • Ubuntu 20.04
  • macOS 10.15
  • macOS 11.0
  • Windows Server 2016 R2
  • Windows Server 2019

Expected behavior

  • My GitHub Action runs the Xcode UI tests and they pass or fail based on the code in the branch that triggered the action
  • The tests should also take a comparable amount of time to run if no new tests are added (approx 15min tops in previous runs). Obviously this does not count time queued.
  • Each job should run once

Actual behavior

  • Jobs can take 1.5-3 hours and fail with the error GitHub Actions has encountered an internal error when running your job..
  • Jobs appear to run multiple times?
  • If a job does run, random tests fail with the error: (full logs)
2021-01-14T06:09:53.2597130Z /Users/runner/work/HighlightedTextEditor/HighlightedTextEditor/Tests/Essayist/iOS-EssayistUITests/iOS_EssayistUITests.swift:130: error: -[iOS_EssayistUITests.iOS_EssayistUITests testAutocapitalizationModifier] : Failed to get launch progress for <XCUIApplicationImpl: 0x600003ce0150 com.kylenazario.Essayist at /Users/runner/Library/Developer/Xcode/DerivedData/Essayist-amfzprbnvltnuodtpdnynupooynw/Build/Products/Debug-iphonesimulator/Essayist.app>: Failed to create app asset promise. Failed to create promise.

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

@miketimofeev
Copy link
Contributor

Hi @kyle-n!
Unfortunately, we are currently experiencing queuing issues with macOS 11.0 and investigating possible ways to handle them. That's probably the root cause of your issues as well. More details can be found in the Announcement #1814

@miketimofeev miketimofeev added bug Something isn't working OS: macOS and removed needs triage labels Jan 15, 2021
@vin-fandemand
Copy link

@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 ?

@miketimofeev
Copy link
Contributor

@vin-fandemand do you mean it takes too much time to compile and run tests in comparison to local build?

@vin-fandemand
Copy link

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.

on:
  workflow_dispatch:
jobs:
  build_ios:
    runs-on: "macos-latest"

@miketimofeev
Copy link
Contributor

@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.

@vin-fandemand
Copy link

@miketimofeev is there a way to make the run faster ? Even if there is a premium charge.

@miketimofeev
Copy link
Contributor

@vin-fandemand, unfortunately, no, at least at the moment. We're continuously working on several improvements, but no ETA for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Apple bug Something isn't working OS: macOS
Projects
None yet
Development

No branches or pull requests

3 participants