search

DevExpress / testcafe-browser-provider-saucelabs

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

ERROR Error: Could not start Sauce Connect. Exit code 2 signal: null #44

Closed GregoryCBT closed 5 years ago

GregoryCBT commented 5 years ago

Test won't start due to this error appearing during testcafe startup. I have SAUCE_USERNAME and SAUCE_ACCESS_KEY set up correctly and testcafe -b saucelabs when I run it but running any normal test always give the same error.

Here's the command I used to run the test: testcafe "saucelabs:Chrome@beta:Windows 10" test.js -S --selector-timeout 2000 --assertion-timeout 2000

Here's the entire error output: ERROR Error: Could not start Sauce Connect. Exit code 2 signal: null at ChildProcess.<anonymous> (/usr/lib/node_modules/testcafe-browser-provider-saucelabs/node_modules/sauce-connect-launcher/lib/sauce-connect-launcher.js:561:12) at emitTwo (events.js:126:13) at ChildProcess.emit (events.js:214:7) at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)

miherlosev commented 5 years ago

Hi @GregoryCBT

Could please provide us with the log files generated by saucelabs-connector? You can find them in the directory in which you run TestCafe. image

GregoryCBT commented 5 years ago

As far as I can tell testcafe isn't generating any saucelabs-connector log files. I've looked all over and I can't seem to find any log files being generated anywhere.

AndreyBelym commented 5 years ago

Please try to open the node_modules/testcafe-browser-provider-saucelabs/index.js file, find line 349, and replace connectorLogging: false with connectorLogging: true, tunnelLogging: true. After that, TestCafe should start creating log files in the current working directory.

GregoryCBT commented 5 years ago

It still doesn't seem to be outputting any log files after I made the suggested changes.

AndreyBelym commented 5 years ago

Please try to download the Sauce Connect binary from the SauceLabs site: https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy. Try to run it with the following arguments:

sc -u YOUR_SAUCE_USERNAME -k YOUR_SAUCE_ACCESS_KEY --direct-domains *.google.com,*.gstatic.com,*.googleapis.com
sc --doctor -u YOUR_SAUCE_USERNAME -k YOUR_SAUCE_ACCESS_KEY --direct-domains *.google.com,*.gstatic.com,*.googleapis.com
GregoryCBT commented 5 years ago

Trying to run those commands I either get cannot execute binary file: Exec format error or command not found. If this helps at all I'm trying to run all of this in a raspberry pi 3 model B v 1.2

miherlosev commented 5 years ago

Raspberry PI has an ARM architecture. There is no Sauce Connect binary built for ARM. I suggest you contact the SauceLabs support team and request an ARM-compatible binary of Sauce Connect.