-
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
Timeout issues on CI #356
Comments
This is a change introduced in Detox 5.7.0. In order to support apps with Swift we had to compile Detox.framework on the same machine that compiles the app. This is an extra step that runs in Clearly is was not a good idea to compile it during the first test setup (which will always happen in newly bootstrapped VMs, such as Travis build agents). I am working on a fix, moving the framework compilation to a Hang tight. |
cc @doronpr |
…epare to attemp to fix #356 (Timeouts while running detox.init()).
@rotemmiz I'm having the same issue what do you mean by "just increase the timeout" |
* Move Detox.framework compilation to postinstall rather than driver prepare to attemp to fix #356 (Timeouts while running detox.init()). * fixed postinstall issues * only build iOS source package on mac
@rotemmiz Which version includes this fix? Is there a release yet? |
@DanielMSchmidt it was merged after build passed, but master fails now, I'll make sure it passes before releasing. |
@DanielMSchmidt , 5.9.3 is out |
Description
I wanted to E2E test my project and created a new
react-native init
generated project with a very simple test. Running this locally worked, on CI the tests seem to be hanging.Steps to Reproduce
I am not exactly sure what exactly lead to this problem, but my test config looks like this.
My travis config is a matrix one because I want to support web and native and looks quite similar to the one in detox.
Detox, Node, Device, Xcode and macOS Versions
Detox: 5.9.1
Node: 8.7
Device: Travis
Xcode: 9
macOS: Travis
react-native: 0.49.3
Device and verbose Detox logs
The complete logs are on Travis, but the main error looks like this:
The text was updated successfully, but these errors were encountered: