I might not use it correctly, but i followed the readme instructions and the link to the documentation is a dead link. Can somebody help me, maybe by adding a little code snippet to run a "hello world" test on certain browsers?
I was expecting it to at least print:
"Sauce Connect ready"
"Closed Sauce Connect process"
This is my code
var sauceConnectLauncher = require('sauce-connect-launcher')
var options = {
username: process.env.SAUCE_USER,
accessKey: process.env.SAUCE_GUID,
tunnelIdentifier: process.env.TUNNEL_IDENTIFIER,
verbose: true,
verboseDebugging: true,
vv: true,
logger: console.log
}
sauceConnectLauncher(options, function (err, sauceConnectProcess) {
if (err) return console.error(err.message)
console.log("Sauce Connect ready")
sauceConnectProcess.close(function () {
console.log("Closed Sauce Connect process")
})
})This is my log
Opening local tunnel using Sauce Connect
Starting sc with args: -u XXXXXXXX -k XXXXXXXX --verbose -vv --readyfile /tmp/sc-launcher-readyfile
13 Feb 20:42:05 - Sauce Connect 4.4.3, build 3212 0edd00b-dirty
13 Feb 20:42:05 - Using CA certificate bundle /etc/ssl/certs/ca-certificates.crt.
13 Feb 20:42:05 - Using CA certificate verify path /etc/ssl/certs.
13 Feb 20:42:05 - *** WARNING: open file limit 4096 is too low!
13 Feb 20:42:05 - *** Sauce Labs recommends setting it to at least 8000.
13 Feb 20:42:05 - Starting up; pid 23166
13 Feb 20:42:05 - Command line arguments: /home/serapath/Desktop/dev/holding/orgs/fairydust.agency/projects/ethereum-project/browser-solidity/node_modules/sauce-connect-launcher/sc/sc-4.4.3-linux/bin/sc -u fairydust.work -k **** --verbose -vv --readyfile /tmp/sc-launcher-readyfile
13 Feb 20:42:05 - Log file: /tmp/sc.log
13 Feb 20:42:05 - Pid file: /tmp/sc_client.pid
13 Feb 20:42:05 - Timezone: CET GMT offset: 1h
13 Feb 20:42:05 - Using no proxy for connecting to Sauce Labs REST API.
13 Feb 20:42:06 - Resolving saucelabs.com to 162.222.75.243 took 2944 ms.
13 Feb 20:42:07 - Started scproxy on port 48033.
13 Feb 20:42:07 - Please wait for 'you may start your tests' to start your tests.
Creating tunnel with Sauce Labs
13 Feb 20:42:07 - Starting secure remote tunnel VM...
13 Feb 20:42:14 - Secure remote tunnel VM provisioned.
13 Feb 20:42:14 - Tunnel ID: 224ca5148d634cf384d2792c5b80da4b
13 Feb 20:42:15 - Secure remote tunnel VM is now: booting
13 Feb 20:42:17 - Secure remote tunnel VM is now: running
13 Feb 20:42:17 - Using no proxy for connecting to tunnel VM.
13 Feb 20:42:17 - Resolving tunnel hostname to 162.222.75.76 took 60ms.
13 Feb 20:42:17 - Starting Selenium listener...
13 Feb 20:42:17 - Establishing secure TLS connection to tunnel...
13 Feb 20:42:17 - Selenium listener started on port 4445.
13 Feb 20:43:31 - Cleaning up.
13 Feb 20:43:31 - Removing tunnel 224ca5148d634cf384d2792c5b80da4b.
13 Feb 20:43:36 - All jobs using tunnel have finished.
13 Feb 20:43:36 - Waiting for the connection to terminate...
13 Feb 20:43:37 - Connection closed (8).
13 Feb 20:43:37 - Sauce Connect could not establish a connection.
Sauce Connect API failure
13 Feb 20:43:37 - Please check your firewall and proxy settings.
13 Feb 20:43:37 - You can also use sc --doctor to launch Sauce Connect in diagnostic mode.
13 Feb 20:43:37 - Goodbye.
13 Feb 20:43:37 - Sauce Connect could not establish a connection.
I might not use it correctly, but i followed the
readmeinstructions and the link to the documentation is a dead link. Can somebody help me, maybe by adding a little code snippet to run a "hello world" test on certain browsers?I was expecting it to at least print:
This is my code
This is my log