That's why I suggested creating a simple, reproducible example using something that is completely independent from your project and company (the bit where I said to use gebish.org and checking the title at the home page). It will require you to start from scratch on a fresh project but by doing so you might find that starting simple will help you spot the mistake and if there is no mistake on your side and you still have the exact problem as in your other project then I will be able to take a look at it as it will be completely independent from your work project and something you will be able to share with me.
On Mon, Oct 28, 2019 at 8:51 PM Ben Frey <[email protected]> wrote: > Company-proprietary code and all, so I can't, unfortunately. Unless you > can think of a way around that. > > On Monday, October 28, 2019 at 3:39:15 PM UTC-5, Marcin Erdmann wrote: >> >> Yeah, it does not look like you're using 3.9.0. With regards to your >> failure for opening the tunnel - I can't see your full setup so it's >> impossible for me to tell what's going on. >> >> How about setting up a minimum reproducible example and uploading that to >> github? It can be just the simplest of tests going to gebish.org and >> checking the page title. It should expect the creds the same way as in what >> you sent before - via env vars. I can then check it out locally and give it >> a try by providing credentials I know work - the ones I use for Geb's own >> tests. I'm fairly certain that it will allow us to spot the issue quickly. >> >> Marcin >> >> On Mon, Oct 28, 2019 at 6:21 PM Ben Frey <[email protected]> wrote: >> >>> 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 >>> <https://groups.google.com/d/msgid/geb-user/d728439c-e156-48b5-9dd9-c8dc8f05ece1%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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/6bdcfc1d-ede4-48bb-ac64-12b6e656e1f0%40googlegroups.com > <https://groups.google.com/d/msgid/geb-user/6bdcfc1d-ede4-48bb-ac64-12b6e656e1f0%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CA%2B52dQQz7hmo25LJij69dGpDk-0AHA3VsohRKVb3zq02uguKDA%40mail.gmail.com.
