Passing mergeTestResutls as false for the VsTest task. #11352
Merged
Conversation
This file contains 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
nigurr
approved these changes
Sep 17, 2019
|
I am assuming we have an L2 to catch this regression, going forward |
Sure, since we now have this scenario. Will try to do similar L2 like V2 tasks. |
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.
Default value of mergeTestResults is True and this actually archives the attachments as well.
Which causes the code coverage jobs to fail, as they will be looking for the .coverage files.
We actually pass the mergeTestResutls as false in VsTestV2 also, it was a miss from my side in previous change.