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
{{ message }}
This repository has been archived by the owner on Jul 18, 2023. It is now read-only.
Pytest submits the Job to Saucelabs via it's tunnel.
Saucelabs executes the test, send back the results. At the same time, it should close the current opened session for test, but it doesn't.
This open session as a pytest worker associated with it gw0, gw1 etc., worker cannot stop as the session is still open.
The session on the saucelabs will stay open indefinitely, until a interrupt from within saucelab is triggered. This interrupt would kill -9 the open session without notifying the pytest worker.
In out automation, worker wait's indefinitely to receive data from sauce session.
Mostly occurs in long running tests, randomly in tier2 and tier3. Now that we know the issue, I will look into if we could add a timeout to workers executing tests and later identify all those test and re-check their logic
No description provided.
The text was updated successfully, but these errors were encountered: