Fix the hang issue in Travis CI build triggered by the [Feature] tag#4536
Merged
adityapatwardhan merged 3 commits intoPowerShell:masterfrom Aug 9, 2017
Merged
Fix the hang issue in Travis CI build triggered by the [Feature] tag#4536adityapatwardhan merged 3 commits intoPowerShell:masterfrom
adityapatwardhan merged 3 commits intoPowerShell:masterfrom
Conversation
TravisEz13
approved these changes
Aug 9, 2017
Member
Author
|
The failures in AppVeyor are all |
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
4 participants
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.
Some class related parser tests may cause Travis build to hang if they are running with CrossGen'ed assemblies. This is an issue to the CrossGen utility, and it's tracked by https://github.com/dotnet/coreclr/issues/9745.
To work around the issue, we made the following changes to our build:
The recent
[Feature]tag support allows us to run the full build in PR or Commit-Push CI builds. The parser tests should run in those[Feature]tag builds, so we need to make sure the[Feature]tag builds don't use-CrossGenbefore running the tests.Two other changes: