Skip to content

"Error: request aborted" on >= v0.3.0 #39

Closed

Description

@kellyselden

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.

Activity

  1. rwjblue commented on Sep 15, 2016

    @rwjblue
    Collaborator

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

  2. kellyselden commented on Sep 15, 2016

    @kellyselden
    CollaboratorAuthor

    phantom and qunit

  3. tylergets commented on Sep 15, 2016

    @tylergets

    Having the same issue.

  4. denchen commented on Sep 21, 2016

    @denchen

    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.

  5. nathanpalmer commented on Sep 24, 2016

    @nathanpalmer

    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).

  6. joshsmith commented on Oct 5, 2016

    @joshsmith

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

  7. kategengler commented on Oct 31, 2016

    @kategengler
    Collaborator

    #57 seems similar

  8. baseballlover723 commented on Nov 13, 2016

    @baseballlover723

    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

  9. JoannaFalkowska commented on Nov 17, 2016

    @JoannaFalkowska

    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.

  10. kategengler commented on Nov 17, 2016

    @kategengler
    Collaborator

    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
  11. chrisvdp commented on Nov 18, 2016

    @chrisvdp
    Contributor

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

  12. Cryrivers commented on Nov 23, 2016

    @Cryrivers

    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.

  13. adhamhf commented on Dec 12, 2016

    @adhamhf

    "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

  14. andrew-zenefits commented on Dec 13, 2016

    @andrew-zenefits

    "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

  15. ethanrubio commented on Dec 20, 2016

    @ethanrubio

    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

  16. wagenet commented on Dec 22, 2016

    @wagenet
    Contributor

    Appears to be fixed by #82

  17. kellyselden commented on Dec 22, 2016

    @kellyselden
    CollaboratorAuthor

    Just tried it out. Works for me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions