setScriptTimeout (allScriptsTimeout) fails in SauceLabs (http://saucelabs.com) and there is no option to disable it

[renatoch]

Bug report

• Node Version: 8.11.3

• Protractor Version: 5.3.0

• Angular Version: 1.3.0

• Browser(s): chrome

• Operating System and Version windows 10

• Your protractor configuration file config.txt

• A relevant example test

• Output from running the test {"message":"unknown error: 'ms' must be a double\n (Session info: chrome=67.0.3396.62)\n (Driver info: chromedriver=2.39.562718 (9a2698cba08cf5a471a29d30c8b3e12becabb0e9),platform=Windows NT 6.3.9600 x86_64)"}

• Steps to reproduce the bug -- Just run any test in SauceLabs (http://saucelabs.com)

Protractor tries to set setScriptTimeout using value allScriptsTimeout. In SauceLabs, that causes the error reported above, so besides not working, it consumes time from the test run.

https://github.com/angular/protractor/blob/0fbc2c0ac12992bd61712188a96aef6684bef0c1/lib/runner.ts#L281

It could both:

• convert the value to double to make it work
• provide an option to disable this command completely, so I can save this time if I want to

[CrispusDH]

I suggest to use defaultTimeoutInterval only. There is almost the same idea. could you explain what your purpose in using allScriptsTimeout?

[renatoch]

The issue is that protractor runs setScriptTimeout, even if I don't set any value, using the default value 0.

Have a look at the default behavior on the code line I've mentioned, it's executed regardless if the parameter has been set or not.

[joelgrimberg]

@renatoch did you find a fix or workaround for this issue?

[renatoch]

@joelgrim Unfortunately not, I ended up accepting the time loss and ignoring the error messages...