Now running tests as a child process to work around the GC issue #301
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
experienced when running them altogether using TS 2.0 microsoft/TypeScript#11452
Also this PR marks the flaky tests as just that and ensures that they no longer fail the build. Huzzah!
There's some work that could be done to normalize "/" and "" in test results; *nix and Windows differ as ever and cause tests to fail. Also "[built]" sometimes gets placed in the output.txt; causing mismatches. This could probably be excluded from the checks.
Finally this PR also drops the pre TS 2.0 builds from the test matrices (travis and appveyor).
And you know what this means? GREEN TESTS 😄