search

DevExpress / testcafe-browser-provider-saucelabs

This is the Sauce Labs browser provider plugin for TestCafe.
https://devexpress.github.io/testcafe/
MIT License
32 stars 41 forks source link

Error: Could not start Sauce Connect. Exit code 3221225595 signal: null #77

Closed JackSinclairT closed 2 years ago

JackSinclairT commented 3 years ago

Our testcafe tests were running fine on 10/09/2021, however when our tests ran on 11/09/2021 (with no changes made at all on our end) we now get a sauce connect error:

ERROR Was unable to open the browser "saucelabs:Chrome@latest:Windows 10" due to error.

Error: Could not start Sauce Connect. Exit code 3221225595 signal: null
    at ChildProcess.<anonymous> (D:\a\1\test-automation-ui\src\node_modules\sauce-connect-launcher\lib\sauce-connect-launcher.js:566:12)
    at ChildProcess.emit (events.js:310:20)
    at ChildProcess.EventEmitter.emit (domain.js:482:12)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)

We are passing the following env variables through to our testcafe tests: SAUCE_API_HOST SAUCE_CONFIG_PATH SAUCE_ACCESS_KEY SAUCE_USERNAME SAUCE_JOB

These values haven't changed over the course of that time and were working fine all last week. The access key/username is the same as the one on our account too.

HeikoKampe commented 2 years ago

Getting the same error after followed the description in the readme. Node: v14.17.6 Testcafe: 1.15.3 / 1.16.0

miherlosev commented 2 years ago

Hi @JackSinclairT, @HeikoKampe

It's a bug with the new version of the Sauce Connect Proxy Version (4.7.0). At present, you can use the old connector version as a workaround. To do it, you need to create a 'saucelabs-connector-options.json' file (the name may be different) with the following content:

{
    "connectVersion": "4.6.3"
}

After that, specify the file path as the value of the SAUCE_CONNECT_OVERRIDES_PATH environment variable:

set SAUCE_CONNECT_OVERRIDES_PATH=saucelabs-connector-options.json