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
Why do we keep running yarn test:node anyway, even when the build failed? (All the tests basically fail with something like Cannot find module '/home/travis/build/emberjs/ember.js/dist/ember.debug'.)
The text was updated successfully, but these errors were encountered:
We ran into this recently and the problem was dozens of broccoli-babel-transpiler worker processes being spawned and running out of memory. Setting JOBS=2 or something like that can fix it.
This started happening in CI on master recently. It may be related to babel? It seems to only happen in the node tests only.
There are two general problems:
yarn test:node
anyway, even when the build failed? (All the tests basically fail with something likeCannot find module '/home/travis/build/emberjs/ember.js/dist/ember.debug'
.)The text was updated successfully, but these errors were encountered: