You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project work perfectly fine locally with my emulators but when i try to run my tests in the Travis i am facing two problems
When running throught the travis pipeline i first got :
The job exceeded the maximum log length, and has been terminated.
Then i try to log the output in a file which i guess it worked because i get another different "error"
No output has been received in the last 10 minutes
When running with the android emulator :
"detox[4950] ERROR: Error: Exceeded timeout of 30000ms while handling jest-circus "setup" event
detox[4950] INFO: App is assigned to undefined
detox[4950] INFO: App: press button get StepOne text
detox[4950] INFO: App: press button get StepOne text [SKIPPED]
detox[4950] ERROR: DetoxRuntimeError: Aborted detox.init() execution, and now running detox.cleanup()
HINT: Most likely, your test runner is tearing down the suite due to the timeout error
detox[4950] DEBUG: [DetoxServer.js/DISCONNECT] role=tester, sessionId=b10696f2-54a2-aa26-6987-ac125e78ccda
detox[4950] DEBUG: [DetoxServer.js/WS_CLOSE] Detox server connections terminated gracefully
detox[4950] WARN: at node_modules/jest/node_modules/jest-cli/build/cli/index.js:261:15
Jest did not exit one second after the test run has completed.
This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue."
Would appreciate for a little guideline!
The text was updated successfully, but these errors were encountered:
The project work perfectly fine locally with my emulators but when i try to run my tests in the Travis i am facing two problems
Then i try to log the output in a file which i guess it worked because i get another different "error"
Would appreciate for a little guideline!
The text was updated successfully, but these errors were encountered: