Sitelet https://github.com/PowerShell/PowerShell/pull/5521
Skip to content

Fix Import-CliXml Test - #5521

Merged
Ilya (iSazonov) merged 1 commit into
PowerShell:masterfrom
markekraus:FixImportCliXmlTest
Nov 22, 2017
Merged

Ilya (iSazonov) merged 1 commit into
PowerShell:masterfrom
markekraus:FixImportCliXmlTest

Conversation

@markekraus

Copy link
Copy Markdown
Contributor

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.

@markekraus Mark Kraus (markekraus) changed the title Fix Import-CliXml Tests Fix Import-CliXml Test Nov 21, 2017
@iSazonov Ilya (iSazonov) self-assigned this Nov 22, 2017
@iSazonov
Ilya (iSazonov) merged commit 7778941 into PowerShell:master Nov 22, 2017
@TravisEz13 Travis Plunk (TravisEz13) added this to the 6.0.0-GA milestone Nov 29, 2017
Travis Plunk (TravisEz13) pushed a commit to TravisEz13/PowerShell that referenced this pull request Nov 29, 2017
Add checks that ProcessName is not null or empty.
Travis Plunk (TravisEz13) pushed a commit that referenced this pull request Nov 29, 2017
Add checks that ProcessName is not null or empty.
@markekraus
Mark Kraus (markekraus) deleted the FixImportCliXmlTest branch January 19, 2018 18:58
Thatgfsj (Thatgfsj) pushed a commit to Thatgfsj-contribs/PowerShell that referenced this pull request Aug 6, 2026
Add checks that ProcessName is not null or empty.
Thatgfsj (Thatgfsj) pushed a commit to Thatgfsj-contribs/PowerShell that referenced this pull request Aug 6, 2026
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants