Removing thest tests which aren't defined anywhere anymore but the exceptions to skip them are still in place:
* ^mongo - logged (in|out)
* ^logs - logged (in|out)
* ^can't publish package with colons
Since multiple self-tests could run in a series now, this makes sure that when any of them fails, the error is propagated to CircleCI but still lets them all finish.
This reverts commit 7df3ccaa2195af2628f20752104b331997137b73 which introduced a change which required `bash`.
I don't want to force `bash` for a test runner.
This might be overboard as it adds some additional code but the regex off the screen was midly unpleasant.
One additional benefit to this is that you could have a list of excluded tests stored in a separate file and use:
```
ADDL_SELF_TEST_EXCLUDE="$(cat addl_tests.txt)"
```
(note the importance of double quotes to preserve newlines)
This permits changing TIMEOUT_SCALE_FACTOR using a variable instead of hard-coding it in the script.
Also adds ADDL_SELF_TEST_EXCLUDE to define environment specific tests which must be skipped.
For example, I run my preliminary (personal) Meteor tests on SemaphoreCI, but there is a particular test that just _will not work_. This allows me to override particulary problematic tests without sed-ing the script.
This changes the CI script to make sure it runs all tests, regardless of the environment configuration while still allowing flexibility in the size of the container parallelism.
While not having any effect on the Meteor configuration this will now run all 8 test groups across a fewer number of containers, if necessary.
This fixes issues where false-positives are achieved on contributor PRs, like seen on meteor/meteor#7963. I explained here:
https://github.com/meteor/meteor/pull/7963#issuecomment-264188162
This change will also allow the script to run tests in their entirety if the parallelism configuration is missing, such as when run from a local dev box.
The SAVE_DEV_BUNDLE_TARBALL environment variable is already supported in the Unix version and this mimics that functionality in the Windows script. Use of this flag makes debugging much less painful, especially when switching branches (for example, during a `git bisect`) as the dev_bundle can be cached locally.
I also replaced a couple un-related uses of `echo` with `Write-Host` which is the preferred way to output messages in PowerShell as it supports more options.
Fixes: developer experience
Most notably, this update provides error stack traces that include context
from Promise.await calls and await expressions, so (for example) you can
tell where a certain yielding files.* method was originally called,
instead of only getting a useless native stack trace.
