-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
iOS Detox tests fail in Github actions CI with multiple workers - Exceeded timeout of 300000ms while handling jest-circus "setup" event #3574
Comments
I've been experiencing this exact same problem for a while now, the only solution I found was to only use one worker at a time |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this repository, read this discussion. |
The issue has been closed for inactivity. |
Can we reopen this @d4vidi ? |
I'm having this issue on GH Actions after updating the runner from macos-11 to macos-12. It seems the simulator doesn't boot fast enough since its the first use of it. I have maxWorkers at 1.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this repository, read this discussion. |
This is still a problem |
As far as I can tell from the logs, it appears that the simulators refuse to boot:
Even after 7 minutes, they are stuck in the Data Migration step. Here's what a normal boot up looks like:
Something about the Github-actions environment is keeping Detox from creating the simulator dups it needs for concurrency. I don't have a solution for this. I can only propose some words of "wisdom":
|
I've got the same problem with Detox in Microsoft Devops Pipelines, with one worker it works, with more than one, it fails. Same timeout result. |
@d4vidi I'm actually running into this issue without concurrency. So I'm thinking there is some conflict with newer GH runners and Detox |
I'm also running into this same issue and can only run off 1 worker |
Have the same issue running 2 iOS workers on Bitrise CI/CD |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this repository, read this discussion. |
This is still a problem |
any solution |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this repository, read this discussion. |
The issue has been closed for inactivity. |
This is still a problem |
@zacharyweidenbach could you please eleborate on --runner-config e2e/InitCITests/config.json part? |
It is just a pretty standard config file
The test regex was targeting 3 test files called
I am no longer working on the codebase where I had this problem, but I was never able to solve it. |
Thanks for the reply! By "I was never able to solve it" you mean solve with some pretty solution apart from the one you've stated in the topic, or it haven't work at all? |
Sorry, I mean I was never able to solve this problem without the workaround. |
What happened?
First reported with a comment on a separate issue: #3342 (comment)
Running tests for iOS with 3 workers using the detox cli
--workers
leads to intermittent test failures. It seems to have something to do with the instantiation of new simulators to support the concurrent workers. When running only 1 worker, I am unable to reproduce this issue.CI: Github Actions
As a workaround, I have created a simple test suite consisting of only 3 tests. These tests run with 3 workers so that Detox will create new simulator instances for them. This 3 tests usually fail with the timeout issue, however, when the actual test suite runs immediately after, it does not encounter the timeout issue. This leads me to believe that if the simulators have already been created, Detox bypasses this step, and bypasses the bug altogether.
Attached are the logs with
trace
logging enabled from when the errors occurred.The command to run this step is as follows
What was the expected behaviour?
The jest-circus setup step would not timeout.
Was it tested on latest Detox?
Did your test throw out a timeout?
Help us reproduce this issue!
No response
In what environment did this happen?
Detox version: 19.10.0
React Native version: 0.67.2
Node version: 14.18.1
Device model: iPhone 13
iOS version: 14.5
macOS version: 12
Xcode version: 13.4.1
Test-runner (select one): jest-circus
Detox logs
Detox logs
18_Initialize Detox Tests-1.txt
Device logs
Device logs
More data, please!
No response
The text was updated successfully, but these errors were encountered: