Fix Import-CliXml Test #5521
Merged
Fix Import-CliXml Test #5521
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
SteveL-MSFT
approved these changes
Nov 21, 2017
TravisEz13
pushed a commit
to TravisEz13/PowerShell
that referenced
this pull request
Nov 29, 2017
Add checks that ProcessName is not null or empty.
Merged
TravisEz13
pushed a commit
that referenced
this pull request
Nov 29, 2017
Add checks that ProcessName is not null or empty.
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.
I noticed that there was an error in the Import-CliXml context but no failed tests. It turns out this was working because it was exporting null and then checking if null is null.. 馃檨
This fixes the error generated by get-process and ensure the imported values are not null or empty.