"Error: request aborted" on >= v0.3.0 about ember-cli-code-coverage HOT 17 CLOSED

#57 seems similar

from ember-cli-code-coverage.

we are running into the same issue.

Ember CLI: 2.8.0
Running COVERAGE=true ember test

However, running COVERAGE=true ember test --server works.

from ember-cli-code-coverage.

Using phantom? Mocha? Sounds conceptually similar to #32 (in that it sounds related to reading the posted coverage payload).

from ember-cli-code-coverage.

phantom and qunit

from ember-cli-code-coverage.

Having the same issue.

from ember-cli-code-coverage.

I'm seeing the same issue too. I've tried 0.3.1 and 0.3.2, and I get that request aborted message, and there is no /coverage/ directory. I am using [email protected] with this passthrough in /mirage/config.js:

  this.passthrough('/write-coverage');

I went down to 0.2.2 and everything seems to work, and I get coverage information.

from ember-cli-code-coverage.

We're running into something similar. Getting timeouts on 0.3.2. Downgraded to 0.2.2 and it's working fine. We also use ember-cli-mirage@(roughly 0.2.2).

from ember-cli-code-coverage.

Also having the same issue, using Mirage with the passthrough.

from ember-cli-code-coverage.

having the same issue on one of my projects using 0.3.2. Whats weird is that it only sometimes (~50%) happens and only on codeship. I can't reproduce this locally. Downgrading to 0.2.2 seems to of fixed it

from ember-cli-code-coverage.

This happens to me as well 50% of the time on Codeship. I'm using Phantom.

There was similar issue for Blanket: sglanzer-deprecated/ember-cli-blanket#112. It seems that making the request to /write-coverage synchronous might help. Now if I only knew what to change in my code to try it out.

from ember-cli-code-coverage.

The request did change from being sync to async in this commit f2ba0e8#diff-94eab975fb48e219fc130d82e21457ac

However, I have a hunch that this is related to testem version and the fact that a synchronous request fixes it is a patch over the problem, rather than the solution.

For anybody seeing this issue, could you please provide:

• Your ember-cli version
• Whether you're running ember test ember test -s or navigating to /tests

from ember-cli-code-coverage.

"ember-cli": "^2.8.0"
running COVERAGE=true $(npm bin)/ember test in CI

from ember-cli-code-coverage.

"ember-cli": "2.8.0",
"ember-cli-code-coverage": "^0.3.6",
COVERAGE=true ember test --launch phantomjs fails
COVERAGE=true ember test --server works

from ember-cli-code-coverage.

"ember-cli": 2.4.3,
"ember-cli-code-coverage": "^0.3.8",

COVERAGE=true ember t fails
COVERAGE=true ember t -s works (meaning it will update the /coverage/* files

from ember-cli-code-coverage.

Same issue here on circleci. It works locally, however.

"ember-cli": "2.10.0",
"ember-cli-code-coverage": "^0.3.8",

COVERAGE=true ember test fails

from ember-cli-code-coverage.

Appears to be fixed by #82

from ember-cli-code-coverage.

Just tried it out. Works for me!

from ember-cli-code-coverage.