The increased mongo connection timeout in 522d86dc4e
means that the we can decrease the "modules - test app" self-test
application start-up wait internval significantly (since mongo
will now start properly and the self-test can continue).
Certain self-test's like "modules - test app" are encountering
mongo connection timeout errors on some runs. Increasing the
connection timeout helps address these errors.
* Include the Node.js and npm version in the `star.json` manifest.
This makes it possible to know exactly which version of Node.js and npm
were used by the `meteor` command from which the bundle was built from.
* History.md for #8956.
* Add mongo-dev-server package
Only start the MongoDB server if this package
is present in the project.
* Small layout/formatting adjustments; updated README.
* Allow tests using fake-mongod to start (fake) Mongo.
* Adjust test stdout matching to be less sensitive to ordering.
* Add `mongo-dev-server` History.md entry.
* Remove mongo start check since the tested for error prevents mongo startup.
* Remove README traling whitespace.
* Bump mongo package version.
When checking the `entriesByIno` Map to see if an `entry` already exists for
the specified inode, also check to make sure the found `entry` is only
re-used if the current file watcher path matches the returned path. This
makes sure new file watchers are created for moved files (so files with the
same inode), instead of attempting to re-use a file watcher that's watching
an invalid path.
* Fix CircleCI failures by adjusting the timing of problematic tests.
* Wait longer for Mongo to start.
* Increase lint wait time; run logs show we're close to the current timeout.
This implements a non-`galaxy` labeled test (which will run with normal
CI tests) which tests that Galaxy login both fails and succeeds properly
much in the same way that our existing auth tests run except for the
`meteor deploy` command.
With Meteor 1.6 / Node 8, I noticed _buildLocalPackages taking multiple
seconds on initial server startup and restart, and the problem seems to be
that we call the global.gc function too often. This wasn't a problem in
previous versions of Node, as far as I know, but it makes sense to heed
the comment in tools/utils/gc.js, now that it matters.
