Adjusting timeout

[knownasilya]

Adjusting timeout

[knownasilya]

Ah, figured out the issue, I added the option after --u, which gets a url appended to it. We need a comment added to the testem.js saying that no options should be added after that option.

[knownasilya]

Hum, even after adding the option I still get failures. The first launcher runs and succeeds, but the other's fail, e.g.

not ok 164 Browser "ember sauce:launch -b internet explorer -v 11.103 --vi public -p Windows 10 --n MapGeo: Map tests (IE11) --build 576d70bc9f984ace31d1a4c6 --vi public --at --no-ct --u http://localhost:7000/5212/tests/index.html?hidepassed" exited unexpectedly with exit code 1.
not ok 165 Browser "ember sauce:launch -b firefox -v 46.0 --vi public -p Windows 10 --n MapGeo: Map tests (Firefox) --build 576d70bc9f984ace31d1a4c6 --vi public --at --no-ct --u http://localhost:7000/1342/tests/index.html?hidepassed" exited unexpectedly with exit code 1.
not ok 166 Browser "ember sauce:launch -b safari -v 9.0 --vi public -p OS X 10.11 --n MapGeo: Map tests (Safari) --build 576d70bc9f984ace31d1a4c6 --vi public --at --no-ct --u http://localhost:7000/7883/tests/index.html?hidepassed" exited unexpectedly with exit code 1.

There are no jobs in saucelabs for the failed launchers.
Is there a way to know what the error was?

[knownasilya]

Does https://github.com/johanneswuerbach/saucie/blob/master/lib/launch.js#L77 need a catch(..) statement?

Running the tests locally I get:

Browser "ember sauce:launch -b internet explorer -v 11.103 --vi public -p Windows 10 --n MapGeo: Map tests (IE11) --build local --vi public
 --at --no-ct --u http://localhost:7357/2555/tests/index.html?hidepassed" exited unexpectedly with exit code 1.
Stdout:
The option '--b' is not registered with the sauce:launch command. Run `ember sauce:launch --help` for a list of supported options.
The option '--v' is not registered with the sauce:launch command. Run `ember sauce:launch --help` for a list of supported options.
The option '--vi' is not registered with the sauce:launch command. Run `ember sauce:launch --help` for a list of supported options.
The option '--p' is not registered with the sauce:launch command. Run `ember sauce:launch --help` for a list of supported options.
The option '--n' is not registered with the sauce:launch command. Run `ember sauce:launch --help` for a list of supported options.
The option '--build' is not registered with the sauce:launch command. Run `ember sauce:launch --help` for a list of supported options.
The option '--at' is not registered with the sauce:launch command. Run `ember sauce:launch --help` for a list of supported options.
The option '--ct' is not registered with the sauce:launch command. Run `ember sauce:launch --help` for a list of supported options.
The option '--u' is not registered with the sauce:launch command. Run `ember sauce:launch --help` for a list of supported options.
Bail out! Error: [init({"browserName":"internet explorer","version":"11.103","platform":"Windows 10","deviceName":"","device-orientation":"
","tags":["Saucie","test"],"name":"MapGeo: Map tests (IE11)","public":["public","public"],"build":"local","record-video":true})] The enviro
nment you requested was unavailable.

Stderr:
[init({"browserName":"internet explorer","version":"11.103","platform":"Windows 10","deviceName":"","device-orientation":"","tags":["Saucie
","test"],"name":"MapGeo: Map tests (IE11)","public":["public","public"],"build":"local","record-video":true})] The environment you request
ed was unavailable.
Error: [init({"browserName":"internet explorer","version":"11.103","platform":"Windows 10","deviceName":"","device-orientation":"","tags":[
"Saucie","test"],"name":"MapGeo: Map tests (IE11)","public":["public","public"],"build":"local","record-video":true})] The environment you
requested was unavailable.

[johanneswuerbach]

This catch should technically take care of that: https://github.com/johanneswuerbach/saucie/blob/e77cfa07c1bd38fef62d7c7801cae32e04c33639/lib/index.js#L6

Not sure why you are seeing the stderr only locally as both should display this. Maybe the testem reporter is swallowing the error message somehow.

[knownasilya]

Seems like the same thing happens locally and in the CI, but in the CI I cannot see the testem terminal interface that shows me the full error.