You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been toggling between v0.2.2 and v0.3.0 (or v0.3.1) and I'm getting a cryptic error in the new one.
1..1163
# tests 1163
# pass 1141
# skip 22
# fail 0
# ok
Error: request aborted
at IncomingMessage.onAborted (/my-project-path/node_modules/raw-body/index.js:269:10)
at emitNone (events.js:86:13)
at IncomingMessage.emit (events.js:185:7)
at abortIncoming (_http_server.js:280:11)
at Socket.serverSocketCloseListener (_http_server.js:293:5)
at emitOne (events.js:101:20)
at Socket.emit (events.js:188:7)
at TCP._handle.close [as _onclose] (net.js:493:12)
And it doesn't create the coverage folder. It worked fine in the older version. I'm not using mirage or pretender.
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 ember-cli-mirage@0.2.2 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.
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).
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
This happens to me as well 50% of the time on Codeship. I'm using Phantom.
There was similar issue for Blanket: sglanzer-fire/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.
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 testember test -s or navigating to /tests
Activity
rwjblue commentedon Sep 15, 2016
Using phantom? Mocha? Sounds conceptually similar to #32 (in that it sounds related to reading the posted coverage payload).
kellyselden commentedon Sep 15, 2016
phantom and qunit
tylergets commentedon Sep 15, 2016
Having the same issue.
denchen commentedon Sep 21, 2016
I'm seeing the same issue too. I've tried
0.3.1and0.3.2, and I get thatrequest abortedmessage, and there is no/coverage/directory. I am usingember-cli-mirage@0.2.2with this passthrough in/mirage/config.js:I went down to
0.2.2and everything seems to work, and I get coverage information.nathanpalmer commentedon Sep 24, 2016
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).
joshsmith commentedon Oct 5, 2016
Also having the same issue, using Mirage with the passthrough.
kategengler commentedon Oct 31, 2016
#57 seems similar
baseballlover723 commentedon Nov 13, 2016
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
JoannaFalkowska commentedon Nov 17, 2016
This happens to me as well 50% of the time on Codeship. I'm using Phantom.
There was similar issue for Blanket: sglanzer-fire/ember-cli-blanket#112. It seems that making the request to
/write-coveragesynchronous might help. Now if I only knew what to change in my code to try it out.kategengler commentedon Nov 17, 2016
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:
ember testember test -sor navigating to/testschrisvdp commentedon Nov 18, 2016
"ember-cli": "^2.8.0"running
COVERAGE=true $(npm bin)/ember testin CICryrivers commentedon Nov 23, 2016
we are running into the same issue.
Ember CLI: 2.8.0
Running
COVERAGE=true ember testHowever, running
COVERAGE=true ember test --serverworks.adhamhf commentedon Dec 12, 2016
"ember-cli": "2.8.0",
"ember-cli-code-coverage": "^0.3.6",
COVERAGE=true ember test --launch phantomjsfailsCOVERAGE=true ember test --serverworksandrew-zenefits commentedon Dec 13, 2016
"ember-cli": 2.4.3,
"ember-cli-code-coverage": "^0.3.8",
COVERAGE=true ember tfailsCOVERAGE=true ember t -sworks (meaning it will update the/coverage/*filesethanrubio commentedon Dec 20, 2016
Same issue here on circleci. It works locally, however.
"ember-cli": "2.10.0",
"ember-cli-code-coverage": "^0.3.8",
COVERAGE=true ember testfailswagenet commentedon Dec 22, 2016
Appears to be fixed by #82
kellyselden commentedon Dec 22, 2016
Just tried it out. Works for me!