stopServer() never resolves with yarn #198
Comments
|
I have this issue on my mac after |
xg-wang
added a commit
to xg-wang/ember-fetch
that referenced
this issue
Dec 1, 2018
use npm run instead of yarn in travis to work around tomdale/ember-cli-addon-tests#198
xg-wang
added a commit
to xg-wang/ember-fetch
that referenced
this issue
Dec 3, 2018
use npm run instead of yarn in travis to work around tomdale/ember-cli-addon-tests#198
xg-wang
added a commit
to xg-wang/ember-fetch
that referenced
this issue
Dec 3, 2018
use npm run instead of yarn in travis to work around tomdale/ember-cli-addon-tests#198
xg-wang
added a commit
to xg-wang/ember-fetch
that referenced
this issue
Dec 3, 2018
use npm run instead of yarn in travis to work around tomdale/ember-cli-addon-tests#198
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spent the last two hours trying to make tests pass on travis with ember-cli-addon-tests addon.
Turned out that
yarn testfailed, butnpm testpassed. 🤦♂️With yarn the
app.stopServer()promise never resolves. Something in yarn is not letting us kill child processes (which is what stopServer does).The text was updated successfully, but these errors were encountered: