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
We are just getting going with cucumber testing and our cucumber tests were blowing away the data in our development database when setting up the tests, so we decided to go with the mirror option. Unfortunately that doesn't work. Every time the code changes and the server restarts it dies with a failure something like this (thought it's not necessarily the same every time)
=> Server modified -- restarting...
/Users/username/.meteor/packages/coffeescript/.1.0.17.1q4nwrv++os+web.browser+web.cordova/plugin.compileCoffeescript.os/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:116
throw error;
^
Error: ENOENT, symlink '/Users/username/.meteor/packages/meteor/.1.1.14.1lulwc4++os+web.browser+web.cordova/npm/node_modules'
Meteor Mirror exited with code 8
One side-effect is that when the mirror dies, the primary server does not terminate so it has to be manually killed and then restarted to get it going again.
Any idea why this would be happening?
my npm start command looks like this FWIW... "start": "WITH_MIRROR=1 .scripts/start.js"
The text was updated successfully, but these errors were encountered:
On a side note - how do you guys develop without a mirror? If you log in and make a change chimp starts running an @watch test which clears the DB and creates base user accounts which invalidates the login and destroys any active data in dev...
We are just getting going with cucumber testing and our cucumber tests were blowing away the data in our development database when setting up the tests, so we decided to go with the mirror option. Unfortunately that doesn't work. Every time the code changes and the server restarts it dies with a failure something like this (thought it's not necessarily the same every time)
One side-effect is that when the mirror dies, the primary server does not terminate so it has to be manually killed and then restarted to get it going again.
Any idea why this would be happening?
my
npm start
command looks like this FWIW..."start": "WITH_MIRROR=1 .scripts/start.js"
The text was updated successfully, but these errors were encountered: