Closed mikejav closed 1 year ago
Additional note: for now I don't use the more verbose debug mode as this error happens pretty randomly, and when it happened I didn't have the debug mode enabled. I'll try to catch it with the debug mode on.
The anonymized partial logs for the worker that works properly:
and the one that don't:
Note the lack of pipelines-cypress-worker-<worker number here> exited with code 0
at the end of the 2nd case (it's basically a docker container related indicator).
We really need the debug log (for the handing tests) to proceed. Please see here https://github.com/currents-dev/cypress-cloud#troubleshooting. Please reopen and tag me when the debug is enabled
@agoldis the full debug logs contain a lot of data that I can't expose. E.g. the tests/assertions content, project paths etc. Tell me pls - can I omit such data or it's mandatory as well?
@mikejav not necessarily, I need to figure out what's happening after this line of code: https://github.com/currents-dev/cypress-cloud/blob/main/packages/cypress-cloud/lib/run.ts#L140
After I enabled debug mode for currents
- everything started to work as expected. So I disabled debug mode and now this problem is gone. Maybe some cache was cleared out or something.
If I'll catch it once again - I'll send you those logs.
Thanks @agoldis for your assistance :)
Note for future readers. It looks like not a problem with the Currents but with the Cypress itself. https://github.com/cypress-io/cypress/issues/27264
Before opening, please confirm:
Environment information
Describe the bug
I'm executing the tests in parallel using 7 workers. I have 6 projects right now. Sometimes it can happen that when there are no tests to be executed by the worker - the process is gonna finish its work and it prevents e.g. CI check to finish.
Expected behavior
The process exit with code 0.
Command and Setup
nx affected -- --target=currents --browser=chrome
Full log and debug output