For what it's worth, we have a set of WDIO tests that run in SauceLabs just
fine. The config for those is
const sauceConf = {
user: process.env.SAUCE_USERNAME,
key: process.env.SAUCE_ACCESS_KEY,
hostname: 'test.company.com',
path: '/wd/hub',
protocol: 'https',
port: 443,
specs: [
'./tests/business-controls/*/*.js'
],
maxInstances: 14,
capabilities: [
{
maxInstances: 5,
browserName: 'internet explorer',
parentTunnel: 'company',
tunnelIdentifier: 'company-tunnel',
}
],
logLevel: 'warn',
waitforTimeout: 10000,
connectionRetryCount: 5,
services: ['sauce']
};
I notice it's setting up a tunnel, but if I comment out useTunnel = false,
I get this in the logs:
> Task :openSauceTunnelInBackground
Task ':openSauceTunnelInBackground' is not up-to-date because:
Task has not declared any outputs despite executing actions.
> Task :openSauceTunnelInBackground FAILED
:openSauceTunnelInBackground (Thread[Execution worker for ':' Thread 4,5,main])
completed. Took 3 mins 0.163 secs.
:closeSauceTunnel (Thread[Execution worker for ':' Thread 4,5,main]) started.
> Task :closeSauceTunnel
Task ':closeSauceTunnel' is not up-to-date because:
Task has not declared any outputs despite executing actions.
disconnecting tunnel
:closeSauceTunnel (Thread[Execution worker for ':' Thread 4,5,main]) completed.
Took 0.003 secs.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':openSauceTunnelInBackground'.
> Timeout waiting for tunnel to open
On Monday, October 28, 2019 at 8:26:45 AM UTC-5, Ben Frey wrote:
>
> I also found this in the job log; might be relevant? I don't know what "M"
> it's referring to:
> org.openqa.selenium.json.JsonException: Unable to determine type from: M.
> Last 1 characters read: M
> Build info: version: '3.141.59', revision: 'e82be7d358', time:
> '2018-11-14T08:17:03'
> System info: host: 'server', ip: '1.1.1.1', os.name: 'Linux', os.arch:
> 'amd64', os.version: '3.10.0-957.21.3.el7.x86_64', java.version:
> '1.8.0_212'
>
>
> On Monday, October 28, 2019 at 8:12:45 AM UTC-5, Ben Frey wrote:
>>
>> Interesting. Where would I find the version of Selenium I'm using? The
>> only two Selenium dependencies I have in my build.gradle are
>> testCompile 'org.seleniumhq.selenium:selenium-chrome-driver:3.141.59'
>> testCompile 'org.seleniumhq.selenium:selenium-support:3.141.59'
>>
>> So... I don't *think* I'm using 3.9.0, but even when printing out the
>> full dependency tree I don't see anything that looks like a base Selenium
>> library.
>>
>> On Saturday, October 26, 2019 at 4:23:22 PM UTC-5, Marcin Erdmann wrote:
>>>
>>> Ok, so this looks all good to me. I don't see how you'd be passing
>>> anything other than what you see printed as credentials to SauceLabs. So
>>> the only things that come to mind are you are using wrong credentials (are
>>> you sure you're passing in an access key and not a password?) and SauceLabs
>>> is lying that you're passing "None" or you've hit this issue I was able to
>>> find:
>>> https://support.saucelabs.com/hc/en-us/articles/360000921754-Authentication-Error-with-Selenium-3-9-0-Java-Client-Bindings
>>> but
>>> it's unlikely you're using Selenium 3.9.0 as it's been around for quite
>>> some time.
>>>
>>> I've also double checked that nothing has recently changed on the
>>> SauceLabs end and you can still pass creds as part of the URL
>>> (as SauceLabsDriverFactory does) and it has not because Geb's own tests at
>>> SauceLabs do not have any trouble with setting up the driver as of today:
>>> https://circleci.com/gh/geb/geb/2202.
>>>
>>
--
You received this message because you are subscribed to the Google Groups "Geb
User Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/geb-user/d728439c-e156-48b5-9dd9-c8dc8f05ece1%40googlegroups.com.
