johanneswuerbach/ember-cli-sauce

Cross browser testing for your ember-cli app using SauceLabs

ember-cli-sauce's Issues

Testing Edge/Safari always ends with 'Browser disconnected' error

Already lost so many hours on this one, hopefully there is some help! Nevertheless great addon, thumbs up! 👍

So, I always get a Browser disconnected error at the end of a (passing!) testsuite, which Travis then sees as a failed test.

This is the project and the branch where I tried to (fix some Edge issues and) enable Saucelabs testing for Edge: https://github.com/kaliber5/ember-bootstrap/tree/fix-edge. The config files etc. can be found there as well. The basic saucelabs setup is working fine (in the master branch) for Chrome and Firefox, but for Edge and also Safari I always get this error.

Here is an example Travis log: https://travis-ci.org/kaliber5/ember-bootstrap/builds/261632159. Saucelabs itself sees a passing test run: https://saucelabs.com/beta/tests/6d9fd0032d0f4590bd823ec05e7e9fe9

This does not seem to depend on the actual tests, as I said the suite is running without problems on Chrome/FF. I even removed all tests (leaving just linting), and the outcome was still the same. Also I played with the browser_disconnect_timeout setting, but that does not help either (just waits for the specified amount of time until the same error is triggered).

From my naive understanding, it seems as the test suite just runs fine on the remote machine, but somehow Testem is not notified about it having finished, and so continues to wait for some browser output until the timeout kicks in. Does that make sense?

Other browsers other than firefox appears to hang when running tests

On firefox, the tests run and it exits. However, on other browsers such as chrome, and edge, it does not appear to exit, and just hangs there.

Davids-MacBook-Pro-4:mcc dlai$ ember sauce --browser='chrome'
version: 1.13.8
Could not find watchman, falling back to NodeWatcher for file system events.
Visit http://www.ember-cli.com/user-guide/#watchman for more info.
Sauce browser chrome added to your "testem.json" as SL_chrome_public.
Davids-MacBook-Pro-4:mcc dlai$ ember test --launch='SL_chrome_public'
version: 1.13.8
Could not find watchman, falling back to NodeWatcher for file system events.
Visit http://www.ember-cli.com/user-guide/#watchman for more info.
Built project successfully. Stored in "/Users/dlai/projects/mcc/tmp/class-tests_dist-iNY8pS7s.tmp".

** at this point, on sauce labs console, I see the tests finished running. However the browser does not exit so it hangs here continuing to use up sauce minutes.

Tests against microsoft edge are being reported as Chrome 42

Here is the sauce config for my run:
deviceName :
name : Saucie tests
tags : Saucie,test
device-orientation :
tunnel-identifier : PuppetLabs455.corp.puppetlabs.net
platform : Windows 10
browserName : microsoftedge
version : 20
javascriptEnabled : true
public : public
record-video : true

Here's the microsoft edge section in my testem.json:
"SL_edge": {
"exe": "ember",
"args": [
"sauce:launch",
"-b",
"microsoftedge",
"-v",
"20",
"--vi",
"public",
"-p",
"Windows 10",
"--at",
"--no-ct",
"--u"
],
"protocol": "browser"
}

When I execute the command 'ember test --server --port 7000 --launch SL_edge', the tests are run in sauce labs against microsoft edge, but the browser reported in the console is Chrome 42.0

ember test command fails

Getting a similar issue as #42 with Ember-CLI 2.4.3

not ok 1 Browser "ember sauce:launch -b chrome --vi public --at --no-ct --u http://localhost:7357/1769/tests/index.html?hidepassed" failed to connect. testem.js not loaded?
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 '--vi' 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.
# Created remote browser.

1..1
# tests 1
# pass  0
# skip  0
# fail  1

Using 1.5.0 of this addon. The sauce command updated testem.json but I moved the changes to testem.js (and deleted) but still no change.

Your test errored. Test did not see a new command for 90 seconds. Timing out.

The test "fails" in SauceLabs (it fails because of long delay for tests to start but I can see the video of the tests passing) and the terminal returns:

Not all tests passed.
Error: Not all tests passed.
    at EventEmitter.App.getExitCode (/Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/lib/app.js:382:14)
    at EventEmitter.<anonymous> (/Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/lib/app.js:195:39)
    at /Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:726:13
    at /Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:52:16
    at /Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:269:32
    at /Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:44:16
    at /Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:723:17
    at /Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:167:37
    at EventEmitter.App.removeSignalListeners (/Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/lib/app.js:411:5)
    at /Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:718:13
    at iterate (/Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:262:13)
    at /Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:274:29
    at /Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:44:16
    at Server.<anonymous> (/Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:723:17)
    at Server.<anonymous> (/Users/iradchenko/workspace/mapgeo2/map/node_modules/ember-cli/node_modules/testem/node_modules/async/lib/async.js:167:37)
    at Server.g (events.js:260:16)
    at emitNone (events.js:72:20)
    at Server.emit (events.js:166:7)
    at emitCloseNT (net.js:1521:8)
    at nextTickCallbackWith1Arg (node.js:431:9)
    at process._tickCallback (node.js:353:17)

In the SauceLabs logs I see:

 "HTTPStatus": 500,
 "result": "ERROR user closed connection while waiting for command to complete",

Url provided in "ember sauce --help" text is invalid.

https://saucelabs.com/platforms/webdriver does not load. Seems either https://saucelabs.com/platforms/ or https://docs.saucelabs.com/reference/platforms-configurator may be desired.

An in-range update of ember-cli-inject-live-reload is breaking the build 🚨

The devDependency ember-cli-inject-live-reload was updated from 1.8.2 to 1.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-inject-live-reload is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 9 commits.

• 60b2ba2 1.10.0
• 415935b Add yarn.lock.
• 542a2a0 Migrate to lerna-changelog + add 1.10.0 to changelog.
• a21fd1d Merge pull request #55 from SparshithNR/path-fix
• f6d8238 Provide backward compatibility.
• ab29353 Pass path as argument to livereload.js
• 68c237e release v1.9.0 🎉
• 2e88996 Merge pull request #54 from SparshithNR/test-refactor
• fcd41eb Refactoring and Tests

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of ember-export-application-global is breaking the build 🚨

The devDependency ember-export-application-global was updated from 2.0.0 to 2.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-export-application-global is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 2 commits.

• 3641991 Release 2.0.1
• 84999a5 Remove ember-cli-babel dependency.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of ember-data is breaking the build 🚨

Version 2.10.0 of ember-data just got published.

Branch	Build failing 🚨
Dependency	ember-data
Current Version	2.9.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As ember-data is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 65 commits (ahead by 65, behind by 25).

• bda9732 Release Ember Data 2.10.0
• a22a702 Update changelog for the Ember Data 2.10.0 release
• f13827b Release Ember Data v2.10.0-beta.3
• 9ad22ce Update changelog for the Ember Data 2.10.0-beta.3 release
• 7231263 [PERF] fix sub-optimal compiler output (#4655) (#4656)
• f3df538 Release Ember Data 2.10.0-beta.2
• c6aefe7 Update Changelog for the Ember Data 2.10.0-beta.2 release
• 31480e1 [DOC] Add documentation for query#update() to refresh query
• 2b56fdf Release 2.10.0-beta.1
• 7a4beb0 Update changelog for the 2.10.0-beta.1 release
• 6d8e81b Update changelog for Ember Data 2.10.0-beta.1
• 9593e17 Merge pull request #4578 from runspired/fix/null-id-assertions
• 2d464dc fix assertion tests
• 58baca4 fix id in error message
• 97daea8 improved error messaging

There are 65 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Is Mocha supported?

Hi,

I'm encountering some weird behavior with my tests on Sauce Labs. They are passing as far as I can see in the live video but - with a few exceptions - they are reported as failing.

See this one for example: https://saucelabs.com/beta/tests/0595ecfd6e0b4512a37e79aaab550cb9/jsunit

I'm using Mocha and I'm guessing it's the cause of the problem -- but I don't understand why they 'sometimes' pass. It seems that the browser window closes too soon rather than waiting for results to be reported but that's just taking a stab in the dark.

Any ideas?

:)

An in-range update of ember-resolver is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.5.3 of ember-resolver was just published.

Branch	Build failing 🚨
Dependency	ember-resolver
Current Version	4.5.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

ember-resolver is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Allow to set connectVersion via environment

https://github.com/johanneswuerbach/ember-cli-sauce/blob/master/lib/commands/sauce-connect.js#L23 sets various options for the saucie connect method.
With johanneswuerbach/saucie#80 it's also possible to set the connectVersion to that method.

We could expose the connectVersion so an addon consumer could use a newer sauceconnect binary.

Possible environment names: SAUCE_VERSION or others

Adjusting timeout

Is there a way to set timeout? I tried adding --timeout 180 to each launcher args, but that made all of the tests fail. Is the option for sauce:connect?

Support testem default port

Currently the usage of a different port is required to use all browsers on saucelabs. https://github.com/johanneswuerbach/ember-cli-sauce#use-a-different-port

• Report issue to saucelabs
• Create feature request
• Vote on https://saucelabs.ideas.aha.io/ideas/SLIDEA-I-284
• Have 7357 added by default

An in-range update of saucie is breaking the build 🚨

Version 3.3.2 of saucie was just published.

Branch	Build failing 🚨
Dependency	saucie
Current Version	3.3.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

saucie is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 3 commits.

• 24bd186 3.3.2
• f46b515 Merge pull request #84 from chuckcarpenter/bug/invalid-failures
• 89c7b4f update check for global global_test_results and coerce passed to Boolean

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

0.0.7 breaks because it depends on "johanneswuerbach/sauce-js-tests-integration#poll-until-finished" which was deleted

I'm trying to patch htmlbars v0.8.5, which depends on ember-cli-sauce 0.0.7, which has the following dependency:

"saucie": "johanneswuerbach/sauce-js-tests-integration#poll-until-finished"

Looks like that repo is gone, any chance we could bring it back?

Installing addon breaks Broccoli imports for type:test if app is not using QUnit

If an app is not using QUnit, the call QUnit.done in export-test-results.js yields undefined error and kills broccoli imports with type:test causing global variables to not be available from tests folder and potentially breaking unit tests if you use sinon for example.

How do you set the job name?

I've been trying to track down where I can set the job name that is used within SauceLabs. I see it as the "sessionNameSL" option to saucie, but am having troubles finding where I could set it via testem.json or some other place. Any hints are appreciated.

An in-range update of ember-cli-qunit is breaking the build 🚨

The devDependency ember-cli-qunit was updated from 4.3.2 to 4.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-qunit is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of rsvp is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.8.2 of rsvp was just published.

Branch	Build failing 🚨
Dependency	rsvp
Current Version	4.8.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

rsvp is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 4 commits.

• eb32b00 release v4.8.2 🎉
• 3bc9138 update changelog
• 43988f3 Merge pull request #530 from tildeio/revert-491-drop-cast
• b19d137 Revert "drop cast"

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

suggestion for readme

rather then doing:

https://github.com/travis-ci/travis-web/blob/master/testem.json#L12

people should do

scripts: { 'sauce:start: 'ember ....' }

which gives them

npm run sauce:start

ember sauce:launch command fails

Getting a similar issue with 2.4.3

not ok 1 Browser "ember sauce:launch -b chrome --vi public --at --no-ct --u http://localhost:7357/1769/tests/index.html?hidepassed" failed to connect. testem.js not loaded?
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 '--vi' 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.
# Created remote browser.

1..1
# tests 1
# pass  0
# skip  0
# fail  1

Using 1.5.0 of this addon. The sauce command updated testem.json but I moved the changes to testem.js (and deleted) but still no change.

An in-range update of ember-cli-inject-live-reload is breaking the build 🚨

Version 1.8.0 of ember-cli-inject-live-reload was just published.

Branch	Build failing 🚨
Dependency	ember-cli-inject-live-reload
Current Version	1.7.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-inject-live-reload is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 5 commits.

• fcd8ba0 1.8.0
• e06f677 Add 1.8.0 to the CHANGELOG.
• 4b6c25a Merge pull request #49 from SparshithNR/prefix-fix
• 92f52a7 Adding clean-base-url as dependency
• 63b8c66 Consider liveReloadPrefix option which got added into tiny-lr

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

"after all" hook issue in case of Mocha framework

This issue is occurred after adding an 'ember-cli-sauce' package to the project by commit ember-insights/ember-insights@3e330e1.

This is a screen from Chrome. But, the same true for PhantomJS.

This kind of error is occurred once just only for the last JSHint suite, all others are green.

Moreover, these tests are still passed on Sauce Labs, https://saucelabs.com/tests/f1d99075d47f4fb5b3993b3234cfee6f but, my local console shows me report about single passed suite instead of all available. I guess, here is an answer:

153[20.951][INFO]: RESPONSE ExecuteScript {
154 "description": "JSHint - modules/ember-insights/handler.js",
155 "durationSec": 0.001,
156 "passed": true,
157 "specs": [ {
158 "description": "should pass jshint",
159 "durationSec": 0.001,
160 "failedCount": 0,
161 "passed": true,
162 "passedCount": 1,
163 "totalCount": 1
164 } ],
165 "suites": [ ],
166 "totalCount": 1
167}

It looks like a two different bugs just only for Mocha framework. That would be great to get a feedback about that. Thanks.

Reactivate mocha result reporting

Mocha result reporting had to be disabled as it requires access to the mocha runner and the original implementation never worked: #20

PR exposing the runner: ember-cli/ember-cli-mocha#54

Android is reported as Chrome 39.0

Having these testem config:

  "SL_android": {
      "exe": "ember",
      "args": [
        "sauce:launch",
        "-b",
        "android",
        "-dn",
        "Android Emulator",
        "--vi",
        "public",
        "--at",
        "--no-ct",
        "--u"
      ],
      "protocol": "browser"
  }

In Sauce Dashboard Android 5.1 is reported. May be connected to #35.

ember sauce command doesn't support ember-cli ~2.4 due to lack of testem.json file

In ember-cli 2.4, testem.json was migrated to testem.js.
Using ember sauce --browser='firefox' does not add to the testem.js file because it's still looking for the old version

Sauceconnect fails to transmit "all-test-results" event on polling transport

Hi,
I'm trying to figure out why our tests won't complete in Safari 10.
We're getting the usual Browser disconnected error. This error happens if browser_disconnect_timeout is reached.

While looking into the cause, i found out that Testem._isIframeReady never becomes true.
I've added a simple check to see if _isIframeReady ever becomes true:

  setInterval(function(){
    var header =  document.querySelector('#qunit-header');
    if (header) {
      if (Testem._isIframeReady) {
        document.querySelector('#qunit-header').innerText = Date.now() + ' > iframe is ready :D';
      } else {
        document.querySelector('#qunit-header').innerText = Date.now() + ' > iframe is not ready';
      }
    }
  }, 5000);

As it turns out, it doesn't change on saucelabs Safari 10.

Trying the same thing on an ember t --server with a local Safari 10, it'll always connect.

Another weird thing is that loading connection.html usually takes very long (30s+).
I'm not done investigating but it looks like Safari has issues loading the socket/testem connection via sauceconnect.

Sometimes the iframe is ready but the socketio polling fallback returns a 500 for some POST requests.

In general it looks like there's an issue when using the polling socketio transport.
It disconnects and connects again. I guess it can't send the events to the server so it never gets notified that all tests were successful.

It also looks like it sends the correct all-test-results event to the iframe. I guess the testem-client isn't at fault.

I'll investigate further and report back if i find the cause. If anyone has any hints, I'd appreciate.

if /bin/sc fails, the script hangs.

the script should rather exit with the appropriate error code and message.

An in-range update of loader.js is breaking the build 🚨

Version 4.3.0 of loader.js just got published.

Branch	Build failing 🚨
Dependency	loader.js
Current Version	4.2.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As loader.js is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 3 commits .

• d247367 release v4.3.0 🎉
• 31ddcee Merge pull request #117 from ember-cli/runspired-patch-1
• 5ae21dc Remove lib/ from published files.

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Tests don't launch for safari setup

So I've been adding new configurations for my tests, and I get the following:

not ok 472 Browser "ember sauce:launch -b safari -v 9.0 --vi public -p OS X 10.11 --n Map tests (Safari) --build 576ab0fb29f5e2661b84313e --at --no-ct --u http://localhost:7357/5989/tests/index.html?hidepassed" failed to connect. testem.js not loaded?

I have 3 other setups all for Windows and those work without a flaw. I'm going to try another browser on OSX and see if that works..

Provide ability to override default of public for visibility.

May require a change to saucie also?

Would be good to have flag when adding browser for visibility (private, team, etc)

I'll be glad to work on it, if you can point me in the right direction.

command name suggestion:

ember sauce:start
ember sauce:stop

maybe something else, but you should likely namespace your command under sauce:

Move preconnect script into NPM Package?

It makes me somewhat uneasy that the suggested preconnect script is downloaded via curl from a GIST.

Would you be opposed to embedding it into the package as a binary instead? At that point we could enable adding this simple npm script in package.json (or make something like ember sauce connect work):

"scripts": {
  "connect-sauce": "bash ember-cli-sauce_connect-sauce"
}

Individual test failure details are not sent to SauceLabs

Only the counts of how many tests failed are sent. The relevant JSON looks something like

"result": {
  "custom-data": {
    "qunit": {
      "total": 394,
      "failed": 0,
      "runtime": 13933,
      "passed": 394
    }
  },
  "passed": true
}

SauceLabs provides an example of how to gather the test failure results here https://github.com/saucelabs-sample-scripts/JavaScript/blob/master/reporting_QUnit.js

I've got a PR I'll submit soon.

There is one issue where SauceLabs won't display test results if too many failures are sent. In my experience I had to limit it to 15 but I'm not sure if it's the size of the JSON or the number of failures.
https://support.saucelabs.com/customer/portal/questions/16339573-tests-complete-but-does-not-show-test-results

Could not start Sauce Connect. Exit code 1 signal: null

Hello, first time I try the Sauce. I got the below error on this command: ember start-sauce-connect

Could not start Sauce Connect. Exit code 1 signal: null
Could not start Sauce Connect. Exit code 1 signal: null
Error: Could not start Sauce Connect. Exit code 1 signal: null
    at ChildProcess.<anonymous> (/Users/v20100/krc/node_modules/ember-cli-sauce/node_modules/saucie/node_modules/sauce-connect-launcher/lib/sauce-connect-launcher.js:308:16)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)

I did input my access code and key into the Env. Not sure how to fix this.

An in-range update of saucie is breaking the build 🚨

Version 2.1.0 of saucie just got published.

Branch	Build failing 🚨
Dependency	saucie
Current Version	2.0.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As saucie is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v2.1.0

Added

• #55 Allow requesting platform version

Fixed

• #54 Fix device orientation setting

Commits

The new version differs by 5 commits .

• 038fe04 2.1.0
• 20d62bb Merge pull request #55 from simplabs/platform-versions
• 35869ae allow requesting platform version
• d091d5a Merge pull request #54 from simplabs/fix-device-orientation
• 6b9fe17 fix device orientation setting

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of rsvp is breaking the build 🚨

The dependency rsvp was updated from 4.8.4 to 4.8.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rsvp is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 15 commits.

• c473479 release v4.8.5 🎉
• 647215d update changelog
• 856c522 release v4.8.4 🎉
• 0d3c158 release v4.8.3 🎉
• d75af17 update changelog
• 2b8fd20 Merge pull request #539 from tildeio/remove-try-catch-avoidance
• 92aff41 Merge pull request #541 from tildeio/live-reload
• a0a60cb Add livereload yo
• ae46f3d Merge pull request #540 from tildeio/fixpack
• ff10049 Use fixpack
• 98fe2e8 Remove try/catch avoidance, as modern runtimes should not longer need it (a gift to @bmeurer)
• 6dc62ad Merge pull request #538 from loganrosen/master
• 21c4612 Mark all optional parameters using JSDoc syntax
• 36a7eb5 Merge pull request #537 from bekzod/remove-phantom
• 0f1ecae remove phantom

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Live reload causing error during test

I've been having some failing tests on Sauce Labs. After running the failing test manually, I saw that livereload was firing and getting 'connection refused'. I turned off livereload in my ember config and ran it again, tests passed. I don't want to disable livereload in the project because it's still in development.

Has anyone experienced this?
How do I (or do I need to?) disable livereload just for Sauce tests?
Is this a symptom of another problem?

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of ember-cli-babel is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 6.12.0 of ember-cli-babel was just published.

Branch	Build failing 🚨
Dependency	ember-cli-babel
Current Version	6.11.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-babel is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 6 commits.

• d8f266c release v6.12.0 🎉
• fd6c9a6 Merge pull request #204 from kellyselden/_shouldDoNothing
• ea3a2c5 add test
• 5442a39 add a no-op optimization
• 4b68bef Merge pull request #199 from astronomersiva/remove_redundant_check
• 1e1bba9 Remove redundant check for targets

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of ember-cli-sri is breaking the build 🚨

The devDependency ember-cli-sri was updated from 2.1.0 to 2.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-sri is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 4 commits.

• 25a6506 release v2.1.1
• 11eb96d Merge pull request #27 from alobaidizt/whitelist-files
• 1c7b65d Whitelist in package.json only required files
• da9910f Merge pull request #22 from jonathanKingston/bump-version/2.1.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Document adding launchers to testem.json.

Not hard to do, but it would be awesome if the README explained this. Maybe it would be possible to have a command that automatically generate the latest of each of the major browsers?

The following PR is essentially all you need to do: https://github.com/ebryn/filive-demo-app/pull/3/files

An in-range update of loader.js is breaking the build 🚨

Version 4.2.0 of loader.js just got published.

Branch	Build failing 🚨
Dependency	loader.js
Current Version	4.1.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As loader.js is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 14 commits .

• cc53069 release v4.2.0
• 1a453d3 Merge pull request #104 from trentmwillis/redefine
• 93478ef Improve redefinition scenarios
• e289916 Fix test:dev command
• 287a487 Merge pull request #105 from trentmwillis/clarify
• cda1c29 Clarify prime comment
• 562ecf1 Merge pull request #100 from jrowlingson/master
• 6a9b916 remove petal references
• b609262 Merge pull request #95 from chadhietala/heimdall-instrumentation
• c49296d Instrument with heimdall
• 453fe8c Merge pull request #97 from Turbo87/ci-deploy
• 37fef79 CI: Enable automatic NPM deployment for tags
• c4f0755 Merge pull request #96 from chadhietala/dict-registry
• 8a34296 Use dict for registery and seen to avoid filling IC cache

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴