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
Scan execution stuck for 10 minutes after finishing running tests #21461
Comments
Hello, After completing tests with 'fastlane scan', the job stalled for 10 minutes before concluding. The command includes various parameters like test plan, device, and concurrent workers. To troubleshoot, investigate Mayo Clinic Portal potential issues in the post-test phase, considering concurrency settings, simulator availability, and any blocking processes affecting the job's completion. |
This also affects our iOS simultor builds although for us we also also have an additional message displayed after the final test run:
|
I'm seeing the same when running scan with Locally it will hang, but eventually continue after a couple minutes. [Edit: Scratch that - now local build also hangs "indefinitely"] I'm on latest fastlane - Local machine : macOS 13.6, Xcode 14.3 |
We are facing the exact same issue on our Azure pipelines. Any updates? |
I am facing the exac same issue on Github macOS runner. Any updates? Is it sth to do with the tools version? |
We are also experiencing this issue on our self hosted runners. Fastlane 2.213.0 |
Having same issue when building for Xcode 15. Small delay for local building (Apple Silicon) but for Azure Builds (Intel) takes at least 10 minutes |
I'm having the exact same issue on our Jenkins CI. I've try playing around with bunch of the scan options, but with no luck.
The app compiles properly, it runs our tests (in my case UI tests), but it ultimately hangs and return an
|
New Issue Checklist
Issue Description
While running tests on CI, we started getting some weird overall time on a few jobs.
Taking a look at the console output I've noticed that after finishing running tests with
scan
, the execution was stuck for 10 minutes before finishing the job.Command executed
Complete output when running fastlane, including the stack trace and command used
Environment
The text was updated successfully, but these errors were encountered: