Open pavelbabenko opened 1 year ago
I suggest you to set up an open-source demo project with Github Actions so that we can step by step fix and make it work (or identify blockers).
Hello! We appreciate you bringing this issue to our attention. It looks like this could be a valuable addition or fix to our project. We believe that this feature would benefit greatly from contributions from the community, even from first-time contributors.
If you're interested in contributing to this feature, please take a look at our contribution guide. It has all the information you need to know about how to submit a pull request and contribute to our project.
You're also welcome to join our Discord server and discuss this feature with the collaborators or other contributors under the channel 'contributions'.
Please feel free to reach out to us if you have any questions, or need help with anything. We appreciate your feedback and look forward to working with you!
I have a different issue, and I have done some extended debugging on this.... I made a bunch of changes to make sure that the tests work.
a. Make sure it has the --headless flag b. Make sure it DOES NOT have the --cleanup flag
Now I'm stuck at a place where it seems that, even if the tests pass 100%, the process exits with an exit code of 1 due to the an error when it tries to close the detox server.
23:15:51.667 detox[5408] i ipc server socket error Error: read ECONNRESET at Pipe.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -104, code: 'ECONNRESET', syscall: 'read' } 23:15:51.668 detox[5408] i ipc socket disconnected secondary-5434 23:15:51.881 detox[5408] E lifecycle Command failed with exit code = 1:
To add additional information... when the exact same commands are ran on my Mac, it returns a exit code of zero.
I know I'm not necessarily including everything in the logs here, but from what I've seen in the logs, detox invokes the jest process, runs the test... the process returns a EXEC_SUCCESS.... but yet.... the detox command determined that something is wrong and returns a exit code of 1.
Again, this only happens when I try to run it on github actions on a Ubuntu image... the exact same tests runs with a exit code of zero on a Mac.
19:43:19.492 detox[4904] i ipc socket disconnected secondary-4918 19:43:19.493 detox[4918] i ipc connection closed primary-4904 /tmp/detox.primary-4904 0 tries remaining of 0 19:43:19.493 detox[4918] i ipc secondary-4918 exceeded connection rety amount of or stopRetrying flag set. 19:43:19.494 detox[4918] i child-process:EXEC_SUCCESS 19:43:19.754 detox[4904] E lifecycle Command failed with exit code = 1: jest --config e2e/config/config.json e2e
You can fix this in github actions by adding
sudo apt-get install -y libpulse0 libgl1
to your workflow
Anyone in the thread have a GitHub Actions workflow file to share here?
We have an Android macOS GitHub Actions workflow here:
We're still running into the failed with code null
intermittently (it succeeds about 15% of the time):
So we would be happy to try out the Ubuntu workflow if it works!
@karlhorky I've been working on something the last few weeks. You can see what I have so far at https://github.com/oblador/react-native-vector-icons/blob/monorepo/.github/workflows/tests.yaml
Working on getting macosx working this weekend.
Still a work in progress
Description
Hi! I'm trying to run detox tests on Github actions with Ubuntu and having an issue Could you help me with it? Here is a log:
Your environment
Detox version: ^20.1.1 React Native version: 0.70.5 Node version: 16 OS: Ubuntu Test-runner: jest