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 Dec 18, 2019. It is now read-only.
I'm using wdio-sauce-service with remote and it works great with single instance tests, whoever with multiremote shows jobs in saucelabs where we have two browers running in parallel. When the job completes the status in saucelabs is unknown when Passed or Failed would have been expected. Does this work with multiremote, any example config (if relevant?)
Thanks 👍
Environment
wdio-sauce-service 0.4.7
wdio 4.8.0
sauce connect is used via HA setup so no sauceConnect used via the plugin
The text was updated successfully, but these errors were encountered:
would that also resolve the experience in saucelabs where many multiremote tests use the same running sauce VM at the moment causing a timeout eventually (I set 30 mins). Locally I get new instances of 2 chrome instances per multiremote test. I run the tests from wdio runner so don’t see how I can force new browser sessions for multiremote tests. Or is there a way?
Any chance this could be taken up, or is this a very isolated problem not shared by the masses? Using sauce in this way would be a big win vs running on an isolated container
Hi,
I'm using
wdio-sauce-service
with remote and it works great with single instance tests, whoever with multiremote shows jobs in saucelabs where we have two browers running in parallel. When the job completes the status in saucelabs isunknown
when Passed or Failed would have been expected. Does this work with multiremote, any example config (if relevant?)Thanks 👍
Environment
wdio-sauce-service 0.4.7
wdio 4.8.0
sauce connect is used via HA setup so no sauceConnect used via the plugin
The text was updated successfully, but these errors were encountered: