New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BVT/DRT Regressions #543

Closed
vors opened this Issue Feb 12, 2016 · 45 comments

Comments

Projects
None yet
6 participants
@vors
Collaborator

vors commented Feb 12, 2016

BVT/DRT

I made a run of our BVT/DRT tests with FullCLR bits built from GitHub sources.
BVT/DRT are our P0 tests.

Results

BVT: total=500 Pass=496 Fail=4 Error=0 Skip=0 Unspecified=0 Blocked=0 
DRT: total=3248 Pass=3165 Fail=57 Error=8 Skip=4 Unspecified=14 Blocked=0 
P0: total=5891 Pass=5715 Fail=90 Error=0 Skip=72 Unspecified=0 Blocked=14 

Start time 2/12/2016 1:48:03 PM
End time 2/12/2016 2:44:31 PM
Elapsed, 00:56:28.5847284

We take a look to a couple of failures with @JamesWTruher and we observe legitimate problems so far.

Action plan

  • Goal: get a parity in the test results with official windows build
  • We should continue to analyse the rest of results and will provide a simple repro (in form of pester test) where possible. (see example below)
  • We need to incorporate this regression suite in CI process and fix issues.
  • At the same time, we should start to aligning our tests suites (FullPS, LinuxPS, CorePS). This regression test suite is a good starting point for it.
  • Tests should contain info about their origin: a pointer to the original file in a comment.

Example

Describe "BVT/DRT Regression Suite" {
    # original test
    # \monad\tests\mae\PowerShell\tests\Provider\Providers\Lite.Providers.FileSystemProvider.AlternateDataStreams.ps1
    It 'can use alternate AlternateDataStreams with : syntax' {
        $file = [IO.Path]::GetTempFilename()
        Set-Content $file -Stream Stream1 "World"
        cat "${file}:Stream1" | Should Be "World"
    }
}
@vors

This comment has been minimized.

Collaborator

vors commented Feb 13, 2016

Would it make sense to create 'BVT/DRT' label for issues that have been found that way?

@andschwa

This comment has been minimized.

Member

andschwa commented Feb 13, 2016

Yes, I think so.

Can I ask, what is the difference between "failed" and "errored"?

Also, would it be possible to get the test logs? I know the code changes made to monad better than anyone at this point, and could be of some use determining what caused some of the failures.

@vors

This comment has been minimized.

Collaborator

vors commented Feb 13, 2016

Not quite sure about the difference.

So the problem is... it's not that easy :)
Here are 90 errors that I was able to extract with @JamesWTruher
https://github.com/PowerShell/Internal-PowerShellTeam-Tools/blob/master/WTT/Get-WttErrorFromLog.ps1

There could be errors that script cannot parse out and can be found only thru UI. On the other hand, some of the tests are reported more then once, so overall it's a good start.



Title     : Error occurred in test script 'C:\PowerShellTests\PowerShell\tests\Commands\Cmdlets\Clipboard.Tests.ps1'-0
Repro     : Invoke-Pester C:\PowerShellTests\PowerShell\tests\Commands\Cmdlets\Clipboard.Tests.ps1
ErrorText : This command cannot be run due to the error: The system cannot find the file specified. Error occurred in test script 'C:\PowerShellTests\PowerShell\tests\Commands\Cmdlets\Clipboard.Tests.ps1' 
            Failed at <ScriptBlock>, C:\PowerShellTests\PowerShell\tests\Commands\Cmdlets\Clipboard.Tests.ps1: line 184

Title     : MeasureTextCombinationTest
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: Test Failed: 'Flags: TestCharacter.Command returned 0.'    at Microsoft.VS.TTest.Validate.ThrowTestFailureException(String format, Object[] args)    at 
            Microsoft.Test.Management.Automation.MeasureObjectTests.MeasureTextHelper(TestMeasureText flags, String propertyName, Boolean testNoPropertyFound)    at 
            Microsoft.Test.Management.Automation.MeasureObjectTests.MeasureTextCombinationTest()

Title     : TestGetFormatDataAndExportFormatData
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: There were error records output from the script. Id: Microsoft.PowerShell.Commands.WriteErrorException,Assert, Id: ScriptHalted  ---> 
            Microsoft.PowerShell.Commands.WriteErrorException: System.Diagnostics.Process should have four controls '2' does not equal '4'    --- End of inner exception stack trace ---    at 
            Microsoft.Test.Management.Automation.ScriptTestFixture.ExecuteScriptFile(String scriptPath) Parameter 0: C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Commands\TestGetFormatDataAndExportFormatData.ps1 
            Running script: C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Commands\TestGetFormatDataAndExportFormatData.ps1

Title     : ExposeBug1011549
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : System.Management.Automation.CmdletInvocationException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again. ---> 
            System.Management.Automation.PSArgumentException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again.    at 
            System.Management.Automation.CmdletInfo..ctor(String name, Type implementingType, String helpFile, PSSnapInInfo PSSnapin, ExecutionContext context)    at 
            System.Management.Automation.Internal.ModuleUtils.<GetMatchingCommands>d__7.MoveNext()    at Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands(IEnumerable`1 commandNames)    at 
            Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCmdlets()    at Microsoft.PowerShell.Commands.GetCommandCommand.ProcessRecord()    at System.Management.Automation.Cmdlet.DoProcessRecord()    at 
            System.Management.Automation.CommandProcessor.ProcessRecord()    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at 
            Microsoft.Test.Management.Automation.MonadTestHelper.ExecutePipeline(Pipeline pipe, Object[] input, PSObject[]& output, PSObject[]& error)    at 
            Microsoft.Test.Management.Automation.CommandDiscoverySingleShellTest.ExposeBug1011549()

Title     : ExposeBug1018233
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : System.Management.Automation.CmdletInvocationException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again. ---> 
            System.Management.Automation.PSArgumentException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again.    at 
            System.Management.Automation.CmdletInfo..ctor(String name, Type implementingType, String helpFile, PSSnapInInfo PSSnapin, ExecutionContext context)    at 
            System.Management.Automation.Internal.ModuleUtils.<GetMatchingCommands>d__7.MoveNext()    at Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands(IEnumerable`1 commandNames)    at 
            Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands()    at Microsoft.PowerShell.Commands.GetCommandCommand.ProcessRecord()    at System.Management.Automation.Cmdlet.DoProcessRecord()    at 
            System.Management.Automation.CommandProcessor.ProcessRecord()    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at 
            Microsoft.Test.Management.Automation.MonadTestHelper.ExecutePipeline(Pipeline pipe, Object[] input, PSObject[]& output, PSObject[]& error)    at 
            Microsoft.Test.Management.Automation.CommandDiscoverySingleShellTest.ExposeBug1018233()

Title     : ExposeLookupAliasBug1015822
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : System.Management.Automation.CmdletInvocationException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again. ---> 
            System.Management.Automation.PSArgumentException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again.    at 
            System.Management.Automation.CmdletInfo..ctor(String name, Type implementingType, String helpFile, PSSnapInInfo PSSnapin, ExecutionContext context)    at 
            System.Management.Automation.Internal.ModuleUtils.<GetMatchingCommands>d__7.MoveNext()    at Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands(IEnumerable`1 commandNames)    at 
            Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands()    at Microsoft.PowerShell.Commands.GetCommandCommand.ProcessRecord()    at System.Management.Automation.Cmdlet.DoProcessRecord()    at 
            System.Management.Automation.CommandProcessor.ProcessRecord()    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at 
            Microsoft.Test.Management.Automation.MonadTestHelper.ExecutePipeline(Pipeline pipe, Object[] input, PSObject[]& output, PSObject[]& error)    at 
            Microsoft.Test.Management.Automation.CommandDiscoverySingleShellTest.ExposeLookupAliasBug1015822()

Title     : ExposeLookupScriptBug1015822
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : System.Management.Automation.CmdletInvocationException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again. ---> 
            System.Management.Automation.PSArgumentException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again.    at 
            System.Management.Automation.CmdletInfo..ctor(String name, Type implementingType, String helpFile, PSSnapInInfo PSSnapin, ExecutionContext context)    at 
            System.Management.Automation.Internal.ModuleUtils.<GetMatchingCommands>d__7.MoveNext()    at Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands(IEnumerable`1 commandNames)    at 
            Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands()    at Microsoft.PowerShell.Commands.GetCommandCommand.ProcessRecord()    at System.Management.Automation.Cmdlet.DoProcessRecord()    at 
            System.Management.Automation.CommandProcessor.ProcessRecord()    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at 
            Microsoft.Test.Management.Automation.MonadTestHelper.ExecutePipeline(Pipeline pipe, Object[] input, PSObject[]& output, PSObject[]& error)    at 
            Microsoft.Test.Management.Automation.CommandDiscoverySingleShellTest.ExposeLookupScriptBug1015822()

Title     : Bug259687
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: There were error records output from the script. Id: Argument,Microsoft.PowerShell.Commands.GetCommandCommand  ---> System.Management.Automation.PSArgumentException: Cannot process 
            argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again.    at System.Management.Automation.CmdletInfo..ctor(String name, Type implementingType, String 
            helpFile, PSSnapInInfo PSSnapin, ExecutionContext context)    at System.Management.Automation.Internal.ModuleUtils.<GetMatchingCommands>d__7.MoveNext()    at 
            Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands(IEnumerable`1 commandNames)    at Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands()    at 
            Microsoft.PowerShell.Commands.GetCommandCommand.ProcessRecord()    at System.Management.Automation.Cmdlet.DoProcessRecord()    at System.Management.Automation.CommandProcessor.ProcessRecord()    --- End of inner exception 
            stack trace ---    at Microsoft.Test.Management.Automation.ScriptTestFixture.ExecuteScriptFile(String scriptPath) Parameter 0: C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\InitialSessionState\Bug259687.ps1 
            Running script: C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\InitialSessionState\Bug259687.ps1

Title     : ClearHistoryWithValidID
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : System.Management.Automation.CmdletInvocationException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again. ---> 
            System.Management.Automation.PSArgumentException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again.    at 
            System.Management.Automation.CmdletInfo..ctor(String name, Type implementingType, String helpFile, PSSnapInInfo PSSnapin, ExecutionContext context)    at 
            System.Management.Automation.Internal.ModuleUtils.<GetMatchingCommands>d__7.MoveNext()    at Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands(IEnumerable`1 commandNames)    at 
            Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCmdlets()    at Microsoft.PowerShell.Commands.GetCommandCommand.ProcessRecord()    at System.Management.Automation.Cmdlet.DoProcessRecord()    at 
            System.Management.Automation.CommandProcessor.ProcessRecord()    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at 
            Microsoft.PowerShell.Test.SDK.SdkRunspace.ExecuteScript(String cmd, Object[] pipelineInput, Boolean addToHistory)    at Microsoft.Test.Management.Automation.ClearHistoryDRTTests.RunMultipleCommands()    at 
            Microsoft.Test.Management.Automation.ClearHistoryDRTTests.ClearHistoryWithValidID()

Title     : ClearHistoryWithValidCount
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : System.Management.Automation.CmdletInvocationException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again. ---> 
            System.Management.Automation.PSArgumentException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again.    at 
            System.Management.Automation.CmdletInfo..ctor(String name, Type implementingType, String helpFile, PSSnapInInfo PSSnapin, ExecutionContext context)    at 
            System.Management.Automation.Internal.ModuleUtils.<GetMatchingCommands>d__7.MoveNext()    at Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands(IEnumerable`1 commandNames)    at 
            Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCmdlets()    at Microsoft.PowerShell.Commands.GetCommandCommand.ProcessRecord()    at System.Management.Automation.Cmdlet.DoProcessRecord()    at 
            System.Management.Automation.CommandProcessor.ProcessRecord()    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at 
            Microsoft.PowerShell.Test.SDK.SdkRunspace.ExecuteScript(String cmd, Object[] pipelineInput, Boolean addToHistory)    at Microsoft.Test.Management.Automation.ClearHistoryDRTTests.RunMultipleCommands()    at 
            Microsoft.Test.Management.Automation.ClearHistoryDRTTests.ClearHistoryWithValidCount()

Title     : ClearHistoryWithValidCommandLine
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : System.Management.Automation.CmdletInvocationException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again. ---> 
            System.Management.Automation.PSArgumentException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again.    at 
            System.Management.Automation.CmdletInfo..ctor(String name, Type implementingType, String helpFile, PSSnapInInfo PSSnapin, ExecutionContext context)    at 
            System.Management.Automation.Internal.ModuleUtils.<GetMatchingCommands>d__7.MoveNext()    at Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands(IEnumerable`1 commandNames)    at 
            Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCmdlets()    at Microsoft.PowerShell.Commands.GetCommandCommand.ProcessRecord()    at System.Management.Automation.Cmdlet.DoProcessRecord()    at 
            System.Management.Automation.CommandProcessor.ProcessRecord()    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at 
            Microsoft.PowerShell.Test.SDK.SdkRunspace.ExecuteScript(String cmd, Object[] pipelineInput, Boolean addToHistory)    at Microsoft.Test.Management.Automation.ClearHistoryDRTTests.RunMultipleCommands()    at 
            Microsoft.Test.Management.Automation.ClearHistoryDRTTests.ClearHistoryWithValidCommandLine()

Title     : Error occurred in Describe block-0
Repro     : Invoke-Pester C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1
ErrorText : {Retrieving the COM class factory for component with CLSID {795A1D7E-950A-4740-BD3D-5447A4A36606} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). 
            Error occurred in Describe block 
            Failed at C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1:177 char:16, Retrieving the COM class factory for component with CLSID {E7F913FE-F9B9-45E0-9045-97F7C9FCFCB0} failed due to the 
            following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). Error occurred in Describe block 
            Failed at C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1:255 char:16, Retrieving the COM class factory for component with CLSID {A8F62558-D730-42F5-9F8C-5B63BAB8D62C} failed due to the 
            following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). Error occurred in Describe block 
            Failed at C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1:489 char:14}

Title     : Error occurred in Describe block-0
Repro     : Invoke-Pester C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1
ErrorText : {Retrieving the COM class factory for component with CLSID {795A1D7E-950A-4740-BD3D-5447A4A36606} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). 
            Error occurred in Describe block 
            Failed at C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1:177 char:16, Retrieving the COM class factory for component with CLSID {E7F913FE-F9B9-45E0-9045-97F7C9FCFCB0} failed due to the 
            following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). Error occurred in Describe block 
            Failed at C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1:255 char:16, Retrieving the COM class factory for component with CLSID {A8F62558-D730-42F5-9F8C-5B63BAB8D62C} failed due to the 
            following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). Error occurred in Describe block 
            Failed at C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1:489 char:14}

Title     : Error occurred in Describe block-0
Repro     : Invoke-Pester C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1
ErrorText : {Retrieving the COM class factory for component with CLSID {795A1D7E-950A-4740-BD3D-5447A4A36606} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). 
            Error occurred in Describe block 
            Failed at C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1:177 char:16, Retrieving the COM class factory for component with CLSID {E7F913FE-F9B9-45E0-9045-97F7C9FCFCB0} failed due to the 
            following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). Error occurred in Describe block 
            Failed at C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1:255 char:16, Retrieving the COM class factory for component with CLSID {A8F62558-D730-42F5-9F8C-5B63BAB8D62C} failed due to the 
            following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). Error occurred in Describe block 
            Failed at C:\PowerShellTests\PowerShell\tests\Engine\ExtensibleTypeSystem\COM.Tests.ps1:489 char:14}

Title     : CmsMessageCommandsCore
Repro     : .\runlite -suite Instrumentation.Logging.ProtectedEventLogging -pri  -test CmsMessageCommandsCore
ErrorText : Exception calling "Invoke" with "0" argument(s): "The term 'Protect-CmsMessage' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was 
            included, verify that the path is correct and try again." System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "The term 'Protect-CmsMessage' is not recognized as the name 
            of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again." ---> System.Management.Automation.CommandNotFoundException: 
            The term 'Protect-CmsMessage' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.  
              at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at CallSite.Target(Closure , CallSite , Object )    --- End of inner 
            exception stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    at 
            System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)    at 
            System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

Title     : MessageRecipientByCert
Repro     : .\runlite -suite Instrumentation.Logging.ProtectedEventLogging -pri  -test MessageRecipientByCert
ErrorText : Exception calling "Invoke" with "0" argument(s): "The term 'Get-PfxCertificate' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was 
            included, verify that the path is correct and try again." System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "The term 'Get-PfxCertificate' is not recognized as the name 
            of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again." ---> System.Management.Automation.CommandNotFoundException: 
            The term 'Get-PfxCertificate' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.  
              at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at CallSite.Target(Closure , CallSite , Object )    --- End of inner 
            exception stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    at 
            System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)    at 
            System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

Title     : InvokeScriptWithRequiresModule-0
Repro     : Invoke-Pester C:\PowerShellTests\PowerShell\tests\Engine\Modules\Engine.Modules.Enhancements.Tests.ps1
ErrorText : Module enhancement expect no error displayed. See failure information:  InvokeScriptWithRequiresModule 
            Failed at line: 801 in C:\PowerShellTests\PowerShell\tests\Engine\Modules\Engine.Modules.Enhancements.Tests.ps1

Title     : AliasAttributeTestForCmdletAdvFnAndWorkflow-0
Repro     : Invoke-Pester C:\PowerShellTests\PowerShell\tests\Engine\Modules\Engine.Modules.Enhancements.Tests.ps1
ErrorText : 
            Expected value was {}, but should not have been the same AliasAttributeTestForCmdletAdvFnAndWorkflow 
            Failed at line: 1300 in C:\PowerShellTests\PowerShell\tests\Engine\Modules\Engine.Modules.Enhancements.Tests.ps1 1300:         $gmoResult | should not be $null

Title     : Error occurred in test script 'C:\PowerShellTests\PowerShell\tests\Engine\Modules\Followup.Tests.ps1'-0
Repro     : Invoke-Pester C:\PowerShellTests\PowerShell\tests\Engine\Modules\Followup.Tests.ps1
ErrorText : Cannot bind argument to parameter 'Path' because it is null. Error occurred in test script 'C:\PowerShellTests\PowerShell\tests\Engine\Modules\Followup.Tests.ps1' 
            Failed at <ScriptBlock>, C:\PowerShellTests\PowerShell\tests\Engine\Modules\Followup.Tests.ps1: line 17

Title     : Blue91339GetAllCommandsFailsWithWFAsRootmodule
Repro     : .\runlite -suite Engine.Modules.TestFollowup -pri  -test Blue91339GetAllCommandsFailsWithWFAsRootmodule
ErrorText : Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again. System.NotSupportedException: Windows PowerShell Workflow is not 
            supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again.    at 
            System.Management.Automation.Utils.GetAstToWorkflowConverterAndEnsureWorkflowModuleLoaded(ExecutionContext context)    at System.Management.Automation.FunctionOps.DefineWorkflows(ExecutionContext context, ScriptBlockAst 
            scriptBlockAst)

Title     : Verifies Information stream on workflow-0
Repro     : Invoke-Pester C:\PowerShellTests\PowerShell\tests\Engine\Other\Pester.Engine.Other.InformationStream.Tests.ps1
ErrorText : Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again. Verifies Information stream on workflow 
            Failed at line: 53 in C:\PowerShellTests\PowerShell\tests\Engine\Other\Pester.Engine.Other.InformationStream.Tests.ps1

Title     : Verifies InformationVariable in workflow compilation-0
Repro     : Invoke-Pester C:\PowerShellTests\PowerShell\tests\Engine\Other\Pester.Engine.Other.InformationStream.Tests.ps1
ErrorText : Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again. Verifies InformationVariable in workflow compilation 
            Failed at line: 69 in C:\PowerShellTests\PowerShell\tests\Engine\Other\Pester.Engine.Other.InformationStream.Tests.ps1

Title     : LoadFromHomeDirDefault
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: did not load module Test Failed: '1' expected, '0' actual.    at Microsoft.VS.TTest.Validate.ThrowTestFailureException(Object actual, Object expected, String message, Object[] args)  
              at Microsoft.VS.TTest.Validate.AssertEquals[T](T actual, T expected, String format, Object[] args)    at Microsoft.Test.Management.Automation.ModulesAndPackagesTests.LoadFromHomeDirDefault()

Title     : CreateRunspaceValidHostValidConfigurationSuccess
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: get-command get-PfxCertificate -Type Cmdlet should return exactly 1 result! Test Failed: '1' expected, '0' actual.    at Microsoft.VS.TTest.Validate.ThrowTestFailureException(Object 
            actual, Object expected, String message, Object[] args)    at Microsoft.VS.TTest.Validate.AssertEquals[T](T actual, T expected, String format, Object[] args)    at 
            Microsoft.Test.Management.Automation.RunspaceFactoryTests.VerifyCmdletsForRunspace(RunspaceInvoke rspInvoke, ReadOnlyCollection`1 cmdlets)    at 
            Microsoft.Test.Management.Automation.RunspaceFactoryTests.VerifySingleShellRunspaceBeforeOpen(Runspace rsp)    at Microsoft.Test.Management.Automation.RunspaceFactoryTests.CreateRunspaceValidHostValidConfigurationSuccess()

Title     : ObjectParameters
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: There were error records output from the script. Id: NoCOMClassIdentified,Microsoft.PowerShell.Commands.NewObjectCommand, Id: NullArray  ---> 
            System.Management.Automation.RemoteException: Retrieving the COM class factory for component with CLSID {795A1D7E-950A-4740-BD3D-5447A4A36606} failed due to the following error: 80040154 Class not registered (Exception from 
            HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).    --- End of inner exception stack trace ---    at Microsoft.Test.Management.Automation.ScriptTestFixture.ExecuteScriptFile(String scriptPath) Parameter 0: 
            C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\COM\ObjectParameters.ps1 Running script: C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\COM\ObjectParameters.ps1

Title     : winblue_191746_DSCModulePath
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: There were error records output from the script. Id: Microsoft.PowerShell.Commands.WriteErrorException,Assert, Id: ScriptHalted  ---> 
            Microsoft.PowerShell.Commands.WriteErrorException: The PSModulePath should contain '%ProgramFiles%\WindowsPowerShell\Modules' unless the user explicitly changes the value    --- End of inner exception stack trace ---    at 
            Microsoft.Test.Management.Automation.ScriptTestFixture.ExecuteScriptFile(String scriptPath) Parameter 0: C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Modules\winblue_191746_DSCModulePath.ps1 Running 
            script: C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Modules\winblue_191746_DSCModulePath.ps1

Title     : winblue_71908_HelpInfoUriForRemoteModule
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: There were error records output from the script. Id: CommandNotFoundException,Microsoft.PowerShell.Commands.ImportModuleCommand, Id: 
            Microsoft.PowerShell.Commands.WriteErrorException,Assert, Id: ScriptHalted  ---> System.InvalidOperationException: Failed to generate proxies for remote module 'w1tpshys.wzy'.  The term 'Export-PSSession' is not recognized 
            as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. ---> 
            System.Management.Automation.CommandNotFoundException: The term 'Export-PSSession' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was 
            included, verify that the path is correct and try again.    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at 
            System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)    at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, 
            PSDataCollection`1 output, PSInvocationSettings settings)    at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)    at 
            System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)    at System.Management.Automation.PowerShell.Invoke[T](IEnumerable input, IList`1 
            output, PSInvocationSettings settings)    at System.Management.Automation.PowerShell.Invoke[T](IEnumerable input, PSInvocationSettings settings)    at 
            System.Management.Automation.RemoteDiscoveryHelper.<InvokeNestedPowerShell>d__5.MoveNext()    at System.Management.Automation.RemoteDiscoveryHelper.<EnumerateWithCatch>d__12`1.MoveNext()    --- End of inner exception stack 
            trace ---    --- End of inner exception stack trace ---    at Microsoft.Test.Management.Automation.ScriptTestFixture.ExecuteScriptFile(String scriptPath) Parameter 0: 
            C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Modules\winblue_71908_HelpInfoUriForRemoteModule.ps1 Running script: 
            C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Modules\winblue_71908_HelpInfoUriForRemoteModule.ps1

Title     : remoteDiscovery-psSession-cimModule
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: There were error records output from the script. Id: CommandNotFoundException,Microsoft.PowerShell.Commands.ImportModuleCommand, Id: 
            Microsoft.PowerShell.Commands.WriteErrorException,Assert, Id: ScriptHalted  ---> System.InvalidOperationException: Failed to generate proxies for remote module 'remoteDiscoveryTest_CimModule'.  The term 'Export-PSSession' 
            is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. ---> 
            System.Management.Automation.CommandNotFoundException: The term 'Export-PSSession' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was 
            included, verify that the path is correct and try again.    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at 
            System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)    at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, 
            PSDataCollection`1 output, PSInvocationSettings settings)    at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)    at 
            System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)    at System.Management.Automation.PowerShell.Invoke[T](IEnumerable input, IList`1 
            output, PSInvocationSettings settings)    at System.Management.Automation.PowerShell.Invoke[T](IEnumerable input, PSInvocationSettings settings)    at 
            System.Management.Automation.RemoteDiscoveryHelper.<InvokeNestedPowerShell>d__5.MoveNext()    at System.Management.Automation.RemoteDiscoveryHelper.<EnumerateWithCatch>d__12`1.MoveNext()    --- End of inner exception stack 
            trace ---    --- End of inner exception stack trace ---    at Microsoft.Test.Management.Automation.ScriptTestFixture.ExecuteScriptFile(String scriptPath) Parameter 0: 
            C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\RemoteDiscovery\remoteDiscovery-psSession-cimModule.ps1 Running script: 
            C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\RemoteDiscovery\remoteDiscovery-psSession-cimModule.ps1

Title     : remoteDiscovery-psSession-psModule
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: There were error records output from the script. Id: CommandNotFoundException,Microsoft.PowerShell.Commands.ImportModuleCommand, Id: 
            Microsoft.PowerShell.Commands.WriteErrorException,Assert, Id: ScriptHalted  ---> System.InvalidOperationException: Failed to generate proxies for remote module 'remoteDiscoveryTest_PSModule'.  The term 'Export-PSSession' is 
            not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. ---> 
            System.Management.Automation.CommandNotFoundException: The term 'Export-PSSession' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was 
            included, verify that the path is correct and try again.    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at 
            System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)    at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, 
            PSDataCollection`1 output, PSInvocationSettings settings)    at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)    at 
            System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)    at System.Management.Automation.PowerShell.Invoke[T](IEnumerable input, IList`1 
            output, PSInvocationSettings settings)    at System.Management.Automation.PowerShell.Invoke[T](IEnumerable input, PSInvocationSettings settings)    at 
            System.Management.Automation.RemoteDiscoveryHelper.<InvokeNestedPowerShell>d__5.MoveNext()    at System.Management.Automation.RemoteDiscoveryHelper.<EnumerateWithCatch>d__12`1.MoveNext()    --- End of inner exception stack 
            trace ---    --- End of inner exception stack trace ---    at Microsoft.Test.Management.Automation.ScriptTestFixture.ExecuteScriptFile(String scriptPath) Parameter 0: 
            C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\RemoteDiscovery\remoteDiscovery-psSession-psModule.ps1 Running script: 
            C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\RemoteDiscovery\remoteDiscovery-psSession-psModule.ps1

Title     : TestNewPSDriveWithCredential
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: There were error records output from the script. Id: DriveRootError,Microsoft.PowerShell.Commands.NewPSDriveCommand, Id: Microsoft.PowerShell.Commands.WriteErrorException,Assert, Id: 
            DriveNotFound,Microsoft.PowerShell.Commands.RemovePSDriveCommand  ---> System.IO.IOException: The specified drive root "\\DEV-14257-72A\TestNetworkPSDrive" either does not exist, or it is not a folder.    --- End of inner 
            exception stack trace ---    at Microsoft.Test.Management.Automation.ScriptTestFixture.ExecuteScriptFile(String scriptPath) Parameter 0: 
            C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Security\TestNewPSDriveWithCredential.ps1 Running script: 
            C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Security\TestNewPSDriveWithCredential.ps1

Title     : ExposeBug920253
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: Test Failed: 'powershell.exe exit code is FFFA0000, expected FFFB0000'    at Microsoft.VS.TTest.Validate.ThrowTestFailureException(String format, Object[] args)    at 
            Microsoft.VS.TTest.Validate.Assert(Boolean condition, String format, Object[] args)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String 
            expectedOutput, DoStringCompare stringCompareOutput, String expectedError, DoStringCompare stringCompareError, Boolean useUnicode)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, 
            UInt32 expectedExitCode, String expectedOutput, String expectedError, DoStringCompare stringCompareError)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, 
            String expectedOutput, String expectedError)    at System.Management.Automation.Test.StartupTests.ExposeBug920253()

Title     : NonexistingConsoleFileTest
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: Test Failed: 'actual error is , expected Failed to load Windows PowerShell console file "2:24:57PM.psc1". WIN 32 error:'    at 
            Microsoft.VS.TTest.Validate.ThrowTestFailureException(String format, Object[] args)    at Microsoft.VS.TTest.Validate.Assert(Boolean condition, String format, Object[] args)    at 
            System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, DoStringCompare stringCompareOutput, String expectedError, DoStringCompare 
            stringCompareError, Boolean useUnicode)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, String expectedError, DoStringCompare 
            stringCompareError)    at System.Management.Automation.Test.StartupTests.NonexistingConsoleFileTest()

Title     : InvalidConsoleSchemaVersionConsoleFileTest
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: Test Failed: 'actual error is , expected A required element ConsoleSchemaVersion in Windows PowerShell console file "StartupTestsConsoleFile.psc1" is invalid.'    at 
            Microsoft.VS.TTest.Validate.ThrowTestFailureException(String format, Object[] args)    at Microsoft.VS.TTest.Validate.Assert(Boolean condition, String format, Object[] args)    at 
            System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, DoStringCompare stringCompareOutput, String expectedError, DoStringCompare 
            stringCompareError, Boolean useUnicode)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, String expectedError, DoStringCompare 
            stringCompareError)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, String expectedError)

Title     : IncompatibleMonadVersionConsoleFileTest
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: Test Failed: 'actual error is , expected Windows PowerShell terminated with the following error:   Incorrect Windows PowerShell version 9999.99.'    at 
            Microsoft.VS.TTest.Validate.ThrowTestFailureException(String format, Object[] args)    at Microsoft.VS.TTest.Validate.Assert(Boolean condition, String format, Object[] args)    at 
            System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, DoStringCompare stringCompareOutput, String expectedError, DoStringCompare 
            stringCompareError, Boolean useUnicode)    at System.Management.Automation.Test.StartupTests.IncompatibleMonadVersionConsoleFileTest()

Title     : IncorrectMSHConsoleExtensionTest
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: Test Failed: 'actual error is , expected Windows PowerShell console file "cf.mshc1" extension is not psc1. Windows PowerShell console file extension must be psc1.'    at 
            Microsoft.VS.TTest.Validate.ThrowTestFailureException(String format, Object[] args)    at Microsoft.VS.TTest.Validate.Assert(Boolean condition, String format, Object[] args)    at 
            System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, DoStringCompare stringCompareOutput, String expectedError, DoStringCompare 
            stringCompareError, Boolean useUnicode)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, String expectedError, DoStringCompare 
            stringCompareError)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, String expectedError)

Title     : ExposeBug934299NoPSVersionTag
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: Test Failed: 'actual error is , expected Cannot read the Windows PowerShell version from Windows PowerShell console file "StartupTestsConsoleFile.psc1".'    at 
            Microsoft.VS.TTest.Validate.ThrowTestFailureException(String format, Object[] args)    at Microsoft.VS.TTest.Validate.Assert(Boolean condition, String format, Object[] args)    at 
            System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, DoStringCompare stringCompareOutput, String expectedError, DoStringCompare 
            stringCompareError, Boolean useUnicode)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, String expectedError, DoStringCompare 
            stringCompareError)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, String expectedError)

Title     : ExposeBug934299EmptyConsoleSchemaVersion
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: Test Failed: 'actual error is , expected A required element ConsoleSchemaVersion in Windows PowerShell console file "StartupTestsConsoleFile.psc1" is invalid.'    at 
            Microsoft.VS.TTest.Validate.ThrowTestFailureException(String format, Object[] args)    at Microsoft.VS.TTest.Validate.Assert(Boolean condition, String format, Object[] args)    at 
            System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, DoStringCompare stringCompareOutput, String expectedError, DoStringCompare 
            stringCompareError, Boolean useUnicode)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, String expectedError, DoStringCompare 
            stringCompareError)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, String expectedError)

Title     : ExposeBug934299WrongPSConsoleFileTag
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: Test Failed: 'actual error is , expected Cannot locate the required element PSConsoleFile in the Windows PowerShell console file "StartupTestsConsoleFile.psc1".'    at 
            Microsoft.VS.TTest.Validate.ThrowTestFailureException(String format, Object[] args)    at Microsoft.VS.TTest.Validate.Assert(Boolean condition, String format, Object[] args)    at 
            System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, DoStringCompare stringCompareOutput, String expectedError, DoStringCompare 
            stringCompareError, Boolean useUnicode)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, String expectedError, DoStringCompare 
            stringCompareError)    at System.Management.Automation.Test.StartupTests.RedirectedStartupTestHelper(String arg, UInt32 expectedExitCode, String expectedOutput, String expectedError)

Title     : GetPSDriveDetectsNetworkMappedDrive
Repro     : .\runlite -suite Providers.FileSystemProvider.Misc -pri  -test GetPSDriveDetectsNetworkMappedDrive
ErrorText : Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again 
            System.ComponentModel.Win32Exception (0x80004005): Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or 
            shared resource and try again

Title     : RemoveNetworkMappedDrive
Repro     : .\runlite -suite Providers.FileSystemProvider.Misc -pri  -test RemoveNetworkMappedDrive
ErrorText : Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again 
            System.ComponentModel.Win32Exception (0x80004005): Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or 
            shared resource and try again

Title     : ExposeSetLocationUNCProviderQualifiedPathBug
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: Test Failed: 'get-location should return a path of "Microsoft.PowerShell.Core\FileSystem::\\DEV-14257-72A\testtemp" but returned "Microsoft.PowerShell.Core\FileSystem::C:\"'    at 
            Microsoft.VS.TTest.Validate.ThrowTestFailureException(String format, Object[] args)    at System.Management.Automation.Test.FileSystemProviderTest.ExposeSetLocationUNCProviderQualifiedPathBug()

Title     : ExposeSetLocationUNCDirectPathBug
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: Test Failed: 'get-location should return a path of "Microsoft.PowerShell.Core\FileSystem::\\DEV-14257-72A\testtemp" but returned "Microsoft.PowerShell.Core\FileSystem::C:\"'    at 
            Microsoft.VS.TTest.Validate.ThrowTestFailureException(String format, Object[] args)    at System.Management.Automation.Test.FileSystemProviderTest.ExposeSetLocationUNCDirectPathBug()

Title     : ClearContent
Repro     : .\runlite -suite Providers.FileSystemProvider.AlternateDataStreams -pri  -test ClearContent
ErrorText : Cannot find path 'C:\Users\sevoroby\AppData\Local\Temp\tmp9A11.tmp:Stream2' because it does not exist. System.Management.Automation.ItemNotFoundException: Cannot find path 
            'C:\Users\sevoroby\AppData\Local\Temp\tmp9A11.tmp:Stream2' because it does not exist.    at System.Management.Automation.LocationGlobber.ResolveProviderPathFromProviderPath(String providerPath, String providerId, Boolean 
            allowNonexistingPaths, CmdletProviderContext context, CmdletProvider& providerInstance)    at System.Management.Automation.LocationGlobber.ResolvePSPathFromProviderPath(String path, CmdletProviderContext context, Boolean 
            allowNonexistingPaths, Boolean isProviderDirectPath, Boolean isProviderQualifiedPath, CmdletProvider& providerInstance)    at System.Management.Automation.LocationGlobber.GetGlobbedMonadPathsFromMonadPath(String path, 
            Boolean allowNonexistingPaths, CmdletProviderContext context, CmdletProvider& providerInstance)    at System.Management.Automation.LocationGlobber.GetGlobbedProviderPathsFromMonadPath(String path, Boolean 
            allowNonexistingPaths, CmdletProviderContext context, ProviderInfo& provider, CmdletProvider& providerInstance)    at System.Management.Automation.SessionStateInternal.ClearContent(String[] paths, CmdletProviderContext 
            context)    at System.Management.Automation.ContentCmdletProviderIntrinsics.Clear(String path, CmdletProviderContext context)    at Microsoft.PowerShell.Commands.ClearContentCommand.ProcessRecord()

Title     : GetContent
Repro     : .\runlite -suite Providers.FileSystemProvider.AlternateDataStreams -pri  -test GetContent
ErrorText : Cannot find path 'C:\Users\sevoroby\AppData\Local\Temp\tmp9BD8.tmp::$DATA' because it does not exist. System.Management.Automation.ItemNotFoundException: Cannot find path 
            'C:\Users\sevoroby\AppData\Local\Temp\tmp9BD8.tmp::$DATA' because it does not exist.    at System.Management.Automation.LocationGlobber.ResolveProviderPathFromProviderPath(String providerPath, String providerId, Boolean 
            allowNonexistingPaths, CmdletProviderContext context, CmdletProvider& providerInstance)    at System.Management.Automation.LocationGlobber.ResolvePSPathFromProviderPath(String path, CmdletProviderContext context, Boolean 
            allowNonexistingPaths, Boolean isProviderDirectPath, Boolean isProviderQualifiedPath, CmdletProvider& providerInstance)    at System.Management.Automation.LocationGlobber.GetGlobbedMonadPathsFromMonadPath(String path, 
            Boolean allowNonexistingPaths, CmdletProviderContext context, CmdletProvider& providerInstance)    at System.Management.Automation.PathIntrinsics.GetResolvedPSPathFromPSPath(String path, CmdletProviderContext context)    at 
            Microsoft.PowerShell.Commands.ContentCommandBase.ResolvePaths(String[] pathsToResolve, Boolean allowNonexistingPaths, Boolean allowEmptyResult, CmdletProviderContext currentCommandContext)

Title     : GetItem
Repro     : .\runlite -suite Providers.FileSystemProvider.AlternateDataStreams -pri  -test GetItem
ErrorText : Cannot find path 'C:\Users\sevoroby\AppData\Local\Temp\tmp9D30.tmp::$DATA' because it does not exist. System.Management.Automation.ItemNotFoundException: Cannot find path 
            'C:\Users\sevoroby\AppData\Local\Temp\tmp9D30.tmp::$DATA' because it does not exist.    at System.Management.Automation.LocationGlobber.ExpandMshGlobPath(String path, Boolean allowNonexistingPaths, PSDriveInfo drive, 
            ContainerCmdletProvider provider, CmdletProviderContext context)    at System.Management.Automation.LocationGlobber.ResolveDriveQualifiedPath(String path, CmdletProviderContext context, Boolean allowNonexistingPaths, 
            CmdletProvider& providerInstance)    at System.Management.Automation.LocationGlobber.GetGlobbedMonadPathsFromMonadPath(String path, Boolean allowNonexistingPaths, CmdletProviderContext context, CmdletProvider& 
            providerInstance)    at System.Management.Automation.LocationGlobber.GetGlobbedProviderPathsFromMonadPath(String path, Boolean allowNonexistingPaths, CmdletProviderContext context, ProviderInfo& provider, CmdletProvider& 
            providerInstance)    at System.Management.Automation.SessionStateInternal.GetItem(String[] paths, CmdletProviderContext context)    at System.Management.Automation.ItemCmdletProviderIntrinsics.Get(String path, 
            CmdletProviderContext context)    at Microsoft.PowerShell.Commands.GetItemCommand.ProcessRecord()

Title     : GetItemMultipleStreams
Repro     : .\runlite -suite Providers.FileSystemProvider.AlternateDataStreams -pri  -test GetItemMultipleStreams
ErrorText : Cannot find path 'C:\Users\sevoroby\AppData\Local\Temp\tmp9E1C.tmp:Stream1' because it does not exist. System.Management.Automation.ItemNotFoundException: Cannot find path 
            'C:\Users\sevoroby\AppData\Local\Temp\tmp9E1C.tmp:Stream1' because it does not exist.    at System.Management.Automation.LocationGlobber.ExpandMshGlobPath(String path, Boolean allowNonexistingPaths, PSDriveInfo drive, 
            ContainerCmdletProvider provider, CmdletProviderContext context)    at System.Management.Automation.LocationGlobber.ResolveDriveQualifiedPath(String path, CmdletProviderContext context, Boolean allowNonexistingPaths, 
            CmdletProvider& providerInstance)    at System.Management.Automation.LocationGlobber.GetGlobbedMonadPathsFromMonadPath(String path, Boolean allowNonexistingPaths, CmdletProviderContext context, CmdletProvider& 
            providerInstance)    at System.Management.Automation.LocationGlobber.GetGlobbedProviderPathsFromMonadPath(String path, Boolean allowNonexistingPaths, CmdletProviderContext context, ProviderInfo& provider, CmdletProvider& 
            providerInstance)    at System.Management.Automation.SessionStateInternal.GetItem(String[] paths, CmdletProviderContext context)    at System.Management.Automation.ItemCmdletProviderIntrinsics.Get(String path, 
            CmdletProviderContext context)    at Microsoft.PowerShell.Commands.GetItemCommand.ProcessRecord()

Title     : RemoveItem
Repro     : .\runlite -suite Providers.FileSystemProvider.AlternateDataStreams -pri  -test RemoveItem
ErrorText : Cannot find path 'C:\Users\sevoroby\AppData\Local\Temp\tmp9F07.tmp:Stream2' because it does not exist. System.Management.Automation.ItemNotFoundException: Cannot find path 
            'C:\Users\sevoroby\AppData\Local\Temp\tmp9F07.tmp:Stream2' because it does not exist.    at System.Management.Automation.LocationGlobber.ResolveProviderPathFromProviderPath(String providerPath, String providerId, Boolean 
            allowNonexistingPaths, CmdletProviderContext context, CmdletProvider& providerInstance)    at System.Management.Automation.LocationGlobber.ResolvePSPathFromProviderPath(String path, CmdletProviderContext context, Boolean 
            allowNonexistingPaths, Boolean isProviderDirectPath, Boolean isProviderQualifiedPath, CmdletProvider& providerInstance)    at System.Management.Automation.LocationGlobber.GetGlobbedMonadPathsFromMonadPath(String path, 
            Boolean allowNonexistingPaths, CmdletProviderContext context, CmdletProvider& providerInstance)    at System.Management.Automation.PathIntrinsics.GetResolvedPSPathFromPSPath(String path, CmdletProviderContext context)    at 
            Microsoft.PowerShell.Commands.RemoveItemCommand.ProcessRecord()

Title     : SetContent
Repro     : .\runlite -suite Providers.FileSystemProvider.AlternateDataStreams -pri  -test SetContent
ErrorText : Exception calling "Invoke" with "0" argument(s): "Should have first content result: 'Updated' does not equal 'World Updated' CallStack: Asserts.ps1: line 87 <- Asserts.ps1: line 219 <- 
            Lite.Providers.FileSystemProvider.AlternateDataStreams.ps1: line 162" System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "Should have first content result: 'Updated' 
            does not equal 'World Updated' CallStack: Asserts.ps1: line 87 <- Asserts.ps1: line 219 <- Lite.Providers.FileSystemProvider.AlternateDataStreams.ps1: line 162" ---> System.Management.Automation.RuntimeException: Should 
            have first content result: 'Updated' does not equal 'World Updated' CallStack: Asserts.ps1: line 87 <- Asserts.ps1: line 219 <- Lite.Providers.FileSystemProvider.AlternateDataStreams.ps1: line 162    at 
            System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at CallSite.Target(Closure , CallSite , Object )    --- End of inner exception 
            stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    at 
            System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)    at 
            System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

Title     : System.Management.Automation.Remoting.UnitTests.WSManPluginEntryDelegatesUnitTests.ConstructionCreatesDelegates
Repro     : 
ErrorText : {System.MethodAccessException: Attempt by method 'System.Management.Automation.Remoting.UnitTests.WSManPluginEntryDelegatesUnitTests.ConstructionCreatesDelegates()' to access method 
            'System.Management.Automation.Remoting.WSManPluginEntryDelegates..ctor()' failed.    at System.Management.Automation.Remoting.UnitTests.WSManPluginEntryDelegatesUnitTests.ConstructionCreatesDelegates(), [HRESULT: 
            0x80131604]. Test operation failed: 'ConstructionCreatesDelegates'.}

Title     : System.Management.Automation.Remoting.UnitTests.WSManPluginEntryDelegatesUnitTests.InitPluginAssignsWorkerPtrs
Repro     : 
ErrorText : {System.MethodAccessException: Attempt by method 'System.Management.Automation.Remoting.UnitTests.WSManPluginEntryDelegatesUnitTests.InitPluginAssignsWorkerPtrs()' to access method 
            'System.Management.Automation.Remoting.WSManPluginEntryDelegates+WSManPluginEntryDelegatesInternal..ctor()' failed.    at 
            System.Management.Automation.Remoting.UnitTests.WSManPluginEntryDelegatesUnitTests.InitPluginAssignsWorkerPtrs(), [HRESULT: 0x80131604]. Test operation failed: 'InitPluginAssignsWorkerPtrs'.}

Title     : System.Management.Automation.Remoting.UnitTests.WSManPluginEntryDelegatesUnitTests.NullInputIsNoOp
Repro     : 
ErrorText : {System.TypeLoadException: Type 'System.Management.Automation.Remoting.UnitTests.SavesErrorCodeWSManPluginFacade' from assembly 'TAEF.WSManPlugin.UnitTests, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' 
            is attempting to implement an inaccessible interface.    at System.Management.Automation.Remoting.UnitTests.WSManPluginEntryDelegatesUnitTests.NullInputIsNoOp(), [HRESULT: 0x80131604]. Test operation failed: 
            'NullInputIsNoOp'.}

Title     : System.Management.Automation.Remoting.UnitTests.WSManPluginShellSessionUnitTests.CloseCommandOperationDoesNothingIfUnmatchedContext
Repro     : 
ErrorText : {System.MethodAccessException: Attempt by method 'System.Management.Automation.Remoting.UnitTests.WSManPluginShellSessionUnitTests.CloseCommandOperationDoesNothingIfUnmatchedContext()' to access method 
            'System.Management.Automation.Remoting.Client.WSManNativeApi+WSManPluginRequest..ctor()' failed.    at 
            System.Management.Automation.Remoting.UnitTests.WSManPluginShellSessionUnitTests.CloseCommandOperationDoesNothingIfUnmatchedContext(), [HRESULT: 0x80131604]. Test operation failed: 
            'CloseCommandOperationDoesNothingIfUnmatchedContext'.}

Title     : System.Management.Automation.Remoting.UnitTests.WSManPluginShellSessionUnitTests.GetCommandSessionReturnsNullIfNoCommandSession
Repro     : 
ErrorText : {System.MethodAccessException: Attempt by method 'System.Management.Automation.Remoting.UnitTests.WSManPluginShellSessionUnitTests.GetCommandSessionReturnsNullIfNoCommandSession()' to access method 
            'System.Management.Automation.Remoting.Client.WSManNativeApi+WSManPluginRequest..ctor()' failed.    at 
            System.Management.Automation.Remoting.UnitTests.WSManPluginShellSessionUnitTests.GetCommandSessionReturnsNullIfNoCommandSession(), [HRESULT: 0x80131604]. Test operation failed: 
            'GetCommandSessionReturnsNullIfNoCommandSession'.}

Title     : DRT - TestCreateProcessPipeName-0
Repro     : 
ErrorText : 

Title     : DRT - TestCreateNamedPipeServer-0
Repro     : 
ErrorText : 

Title     : DRT - TestCreateNamedPipeClient-0
Repro     : 
ErrorText : 

Title     : DRT - TestCreateContainerNamedPipeClient-0
Repro     : 
ErrorText : 

Title     : DRT - TestClientServerConnect-0
Repro     : 
ErrorText : 

Title     : DRT - TestNamedPipeDuplicateServerPipe-0
Repro     : 
ErrorText : 

Title     : DRT - TestNamedPipeClientSessionTransportManager-0
Repro     : 
ErrorText : 

Title     : TestCreateProcessPipeName-0
Repro     : .\runlite -suite PowerShellNamedPipeTests.PowerShellNamedPipeTests -pri  -test TestCreateProcessPipeName-0
ErrorText : Test method PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateProcessPipeName threw exception:  System.MethodAccessException: Attempt by method 
            'PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateProcessPipeName()' to access method 'System.Management.Automation.Remoting.NamedPipeUtils.CreateProcessPipeName(System.Diagnostics.Process)' failed.     at 
            PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateProcessPipeName()       at PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateProcessPipeName()

Title     : TestCreateNamedPipeServer-0
Repro     : .\runlite -suite PowerShellNamedPipeTests.PowerShellNamedPipeTests -pri  -test TestCreateNamedPipeServer-0
ErrorText : Test method PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateNamedPipeServer threw exception:  System.MethodAccessException: Attempt by method 
            'PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateNamedPipeServer()' to access method 'System.Management.Automation.Remoting.RemoteSessionNamedPipeServer..ctor(System.String)' failed.     at 
            PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateNamedPipeServer()       at PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateNamedPipeServer()

Title     : TestCreateNamedPipeClient-0
Repro     : .\runlite -suite PowerShellNamedPipeTests.PowerShellNamedPipeTests -pri  -test TestCreateNamedPipeClient-0
ErrorText : Test method PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateNamedPipeClient threw exception:  System.MethodAccessException: Attempt by method 
            'PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateNamedPipeClient()' to access method 'System.Management.Automation.Remoting.RemoteSessionNamedPipeClient..ctor(System.Diagnostics.Process, System.String)' failed.  
               at PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateNamedPipeClient()       at PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateNamedPipeClient()

Title     : TestCreateContainerNamedPipeClient-0
Repro     : .\runlite -suite PowerShellNamedPipeTests.PowerShellNamedPipeTests -pri  -test TestCreateContainerNamedPipeClient-0
ErrorText : Test method PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateContainerNamedPipeClient threw exception:  System.MethodAccessException: Attempt by method 
            'PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateContainerNamedPipeClient()' to access method 'System.Management.Automation.Remoting.ContainerSessionNamedPipeClient..ctor(Int32, System.String, System.String)' 
            failed.     at PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateContainerNamedPipeClient()       at PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestCreateContainerNamedPipeClient()

Title     : TestClientServerConnect-0
Repro     : .\runlite -suite PowerShellNamedPipeTests.PowerShellNamedPipeTests -pri  -test TestClientServerConnect-0
ErrorText : Test method PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestClientServerConnect threw exception:  System.MethodAccessException: Attempt by method 
            'PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestClientServerConnect()' to access method 'System.Management.Automation.Remoting.RemoteSessionNamedPipeServer..ctor(System.String)' failed.     at 
            PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestClientServerConnect()       at PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestClientServerConnect()

Title     : TestNamedPipeDuplicateServerPipe-0
Repro     : .\runlite -suite PowerShellNamedPipeTests.PowerShellNamedPipeTests -pri  -test TestNamedPipeDuplicateServerPipe-0
ErrorText : Test method PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestNamedPipeDuplicateServerPipe threw exception:  System.MethodAccessException: Attempt by method 
            'PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestNamedPipeDuplicateServerPipe()' to access method 'System.Management.Automation.Remoting.RemoteSessionNamedPipeServer..ctor(System.String)' failed.     at 
            PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestNamedPipeDuplicateServerPipe()       at PowerShellNamedPipeTests.PowerShellNamedPipeTests.TestNamedPipeDuplicateServerPipe()

Title     : TestNamedPipeClientSessionTransportManager-0
Repro     : .\runlite -suite PowerShellNamedPipeTransportTests.PowerShellNamedPipeTransportTests -pri  -test TestNamedPipeClientSessionTransportManager-0
ErrorText : Test method PowerShellNamedPipeTransportTests.PowerShellNamedPipeTransportTests.TestNamedPipeClientSessionTransportManager threw exception:  System.MethodAccessException: Attempt by method 
            'PowerShellNamedPipeTransportTests.PowerShellNamedPipeTransportTests.TestNamedPipeClientSessionTransportManager()' to access method 
            'System.Management.Automation.Remoting.Client.NamedPipeClientSessionTransportManager..ctor(System.Management.Automation.Runspaces.NamedPipeConnectionInfo, System.Guid, 
            System.Management.Automation.Internal.PSRemotingCryptoHelper)' failed.     at PowerShellNamedPipeTransportTests.PowerShellNamedPipeTransportTests.TestNamedPipeClientSessionTransportManager()       at 
            PowerShellNamedPipeTransportTests.PowerShellNamedPipeTransportTests.TestNamedPipeClientSessionTransportManager()

Title     : GetCommandProxyTest
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : System.Management.Automation.CmdletInvocationException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again. ---> 
            System.Management.Automation.PSArgumentException: Cannot process argument because the value of argument "name" is not valid. Change the value of the "name" argument and run the operation again.    at 
            System.Management.Automation.CmdletInfo..ctor(String name, Type implementingType, String helpFile, PSSnapInInfo PSSnapin, ExecutionContext context)    at 
            System.Management.Automation.Internal.ModuleUtils.<GetMatchingCommands>d__7.MoveNext()    at Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCommands(IEnumerable`1 commandNames)    at 
            Microsoft.PowerShell.Commands.GetCommandCommand.AccumulateMatchingCmdlets()    at Microsoft.PowerShell.Commands.GetCommandCommand.ProcessRecord()    at System.Management.Automation.Cmdlet.DoProcessRecord()    at 
            System.Management.Automation.CommandProcessor.ProcessRecord()    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at 
            Microsoft.Test.Management.Automation.MonadTestHelper.ExecutePipeline(Pipeline pipe, Object[] input, PSObject[]& output, PSObject[]& error)    at 
            Microsoft.Test.Management.Automation.ProxyCommandTests.CommonProxyCommandTest(Type commandType)

Title     : ActivityWithScriptBlock
Repro     : .\runlite -suite Scripting.CoreLanguage.CoreFunctionality -pri  -test ActivityWithScriptBlock
ErrorText : Exception calling "Invoke" with "0" argument(s): "Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again." 
            System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell 
            x64-based console, and then try again." ---> System.Management.Automation.RuntimeException: Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based 
            console, and then try again. ---> System.NotSupportedException: Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again.    at 
            System.Management.Automation.Utils.GetAstToWorkflowConverterAndEnsureWorkflowModuleLoaded(ExecutionContext context)    at System.Management.Automation.FunctionOps.DefineWorkflows(ExecutionContext context, ScriptBlockAst 
            scriptBlockAst)    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at 
            CallSite.Target(Closure , CallSite , Object )    --- End of inner exception stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    
            at ExecuteInRunspace(Closure , FunctionContext )

Title     : InlineXamlBlocked
Repro     : .\runlite -suite Scripting.CoreLanguage.CoreFunctionality -pri  -test InlineXamlBlocked
ErrorText : Exception calling "Invoke" with "0" argument(s): "Should not have supported inline XAML: 'InlineXamlNotSupported,Microsoft.PowerShell.Commands.InvokeExpressionCommand' does not equal 
            'System.NotSupportedException,Microsoft.PowerShell.Commands.InvokeExpressionCommand' CallStack: Asserts.ps1: line 87 <- Asserts.ps1: line 219 <- Lite.Scripting.CoreLanguage.CoreFunctionality.ps1: line 259" 
            System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "Should not have supported inline XAML: 'InlineXamlNotSupported,Microsoft.PowerShell.Commands.InvokeExpressionCommand' 
            does not equal 'System.NotSupportedException,Microsoft.PowerShell.Commands.InvokeExpressionCommand' CallStack: Asserts.ps1: line 87 <- Asserts.ps1: line 219 <- Lite.Scripting.CoreLanguage.CoreFunctionality.ps1: line 259" 
            ---> System.Management.Automation.RuntimeException: Should not have supported inline XAML: 'InlineXamlNotSupported,Microsoft.PowerShell.Commands.InvokeExpressionCommand' does not equal 
            'System.NotSupportedException,Microsoft.PowerShell.Commands.InvokeExpressionCommand' CallStack: Asserts.ps1: line 87 <- Asserts.ps1: line 219 <- Lite.Scripting.CoreLanguage.CoreFunctionality.ps1: line 259    at 
            System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at CallSite.Target(Closure , CallSite , Object )    --- End of inner exception 
            stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    at ExecuteInRunspace(Closure , FunctionContext )

Title     : OverwriteWorkflow
Repro     : .\runlite -suite Scripting.CoreLanguage.CoreFunctionality -pri  -test OverwriteWorkflow
ErrorText : Exception calling "Invoke" with "0" argument(s): "Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again." 
            System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell 
            x64-based console, and then try again." ---> System.Management.Automation.RuntimeException: Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based 
            console, and then try again. ---> System.NotSupportedException: Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again.    at 
            System.Management.Automation.Utils.GetAstToWorkflowConverterAndEnsureWorkflowModuleLoaded(ExecutionContext context)    at System.Management.Automation.FunctionOps.DefineWorkflows(ExecutionContext context, ScriptBlockAst 
            scriptBlockAst)    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at 
            CallSite.Target(Closure , CallSite , Object )    --- End of inner exception stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    
            at ExecuteInRunspace(Closure , FunctionContext )

Title     : PowerShellValue
Repro     : .\runlite -suite Scripting.CoreLanguage.CoreFunctionality -pri  -test PowerShellValue
ErrorText : Exception calling "Invoke" with "0" argument(s): "Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again." 
            System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell 
            x64-based console, and then try again." ---> System.Management.Automation.RuntimeException: Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based 
            console, and then try again. ---> System.NotSupportedException: Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again.    at 
            System.Management.Automation.Utils.GetAstToWorkflowConverterAndEnsureWorkflowModuleLoaded(ExecutionContext context)    at System.Management.Automation.FunctionOps.DefineWorkflows(ExecutionContext context, ScriptBlockAst 
            scriptBlockAst)    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at 
            CallSite.Target(Closure , CallSite , Object )    --- End of inner exception stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    
            at ExecuteInRunspace(Closure , FunctionContext )

Title     : StartDebuggingInconsistentState
Repro     : .\runlite -suite Scripting.CoreLanguage.CoreFunctionality -pri  -test StartDebuggingInconsistentState
ErrorText : Exception calling "Invoke" with "0" argument(s): "Should not have been able to start job with inconsistent state: 'CannotSetBreakpointInconsistentLanguageMode,Microsoft.PowerShell.Commands.SetPSBreakpointCommand' does not 
            equal '' CallStack: Asserts.ps1: line 87 <- Asserts.ps1: line 219 <- Lite.Scripting.CoreLanguage.CoreFunctionality.ps1: line 486" System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" 
            argument(s): "Should not have been able to start job with inconsistent state: 'CannotSetBreakpointInconsistentLanguageMode,Microsoft.PowerShell.Commands.SetPSBreakpointCommand' does not equal '' CallStack: Asserts.ps1: line 
            87 <- Asserts.ps1: line 219 <- Lite.Scripting.CoreLanguage.CoreFunctionality.ps1: line 486" ---> System.Management.Automation.RuntimeException: Should not have been able to start job with inconsistent state: 
            'CannotSetBreakpointInconsistentLanguageMode,Microsoft.PowerShell.Commands.SetPSBreakpointCommand' does not equal '' CallStack: Asserts.ps1: line 87 <- Asserts.ps1: line 219 <- 
            Lite.Scripting.CoreLanguage.CoreFunctionality.ps1: line 486    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at 
            CallSite.Target(Closure , CallSite , Object )    --- End of inner exception stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    
            at ExecuteInRunspace(Closure , FunctionContext )

Title     : WorkflowFullLanguage
Repro     : .\runlite -suite Scripting.CoreLanguage.CoreFunctionality -pri  -test WorkflowFullLanguage
ErrorText : Exception calling "Invoke" with "0" argument(s): "Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again." 
            System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell 
            x64-based console, and then try again." ---> System.Management.Automation.RuntimeException: Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based 
            console, and then try again. ---> System.NotSupportedException: Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again.    at 
            System.Management.Automation.Utils.GetAstToWorkflowConverterAndEnsureWorkflowModuleLoaded(ExecutionContext context)    at System.Management.Automation.FunctionOps.DefineWorkflows(ExecutionContext context, ScriptBlockAst 
            scriptBlockAst)    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at 
            CallSite.Target(Closure , CallSite , Object )    --- End of inner exception stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    
            at ExecuteInRunspace(Closure , FunctionContext )

Title     : WorkflowInlineScript
Repro     : .\runlite -suite Scripting.CoreLanguage.CoreFunctionality -pri  -test WorkflowInlineScript
ErrorText : Exception calling "Invoke" with "0" argument(s): "Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again." 
            System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell 
            x64-based console, and then try again." ---> System.Management.Automation.RuntimeException: Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based 
            console, and then try again. ---> System.NotSupportedException: Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again.    at 
            System.Management.Automation.Utils.GetAstToWorkflowConverterAndEnsureWorkflowModuleLoaded(ExecutionContext context)    at System.Management.Automation.FunctionOps.DefineWorkflows(ExecutionContext context, ScriptBlockAst 
            scriptBlockAst)    --- End of inner exception stack trace ---    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at 
            CallSite.Target(Closure , CallSite , Object )    --- End of inner exception stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    
            at ExecuteInRunspace(Closure , FunctionContext )

Title     : WorkflowNativeActivityNotSupported
Repro     : .\runlite -suite Scripting.CoreLanguage.CoreFunctionality -pri  -test WorkflowNativeActivityNotSupported
ErrorText : Exception calling "Invoke" with "0" argument(s): "Should have received an error from excluded activity: 'CommandNotFound,Microsoft.PowerShell.Commands.InvokeExpressionCommand' does not equal 
            'System.NotSupportedException,Microsoft.PowerShell.Commands.InvokeExpressionCommand' CallStack: Asserts.ps1: line 87 <- Asserts.ps1: line 219 <- Lite.Scripting.CoreLanguage.CoreFunctionality.ps1: line 238" 
            System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "Should have received an error from excluded activity: 
            'CommandNotFound,Microsoft.PowerShell.Commands.InvokeExpressionCommand' does not equal 'System.NotSupportedException,Microsoft.PowerShell.Commands.InvokeExpressionCommand' CallStack: Asserts.ps1: line 87 <- Asserts.ps1: 
            line 219 <- Lite.Scripting.CoreLanguage.CoreFunctionality.ps1: line 238" ---> System.Management.Automation.RuntimeException: Should have received an error from excluded activity: 
            'CommandNotFound,Microsoft.PowerShell.Commands.InvokeExpressionCommand' does not equal 'System.NotSupportedException,Microsoft.PowerShell.Commands.InvokeExpressionCommand' CallStack: Asserts.ps1: line 87 <- Asserts.ps1: 
            line 219 <- Lite.Scripting.CoreLanguage.CoreFunctionality.ps1: line 238    at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    
            at CallSite.Target(Closure , CallSite , Object )    --- End of inner exception stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)  
              at ExecuteInRunspace(Closure , FunctionContext )

Title     : ScriptCmdletUnderConstrainedLanguageFailing
Repro     : .\runlite -suite Scripting.CoreLanguage.CoreLanguageTest -pri  -test ScriptCmdletUnderConstrainedLanguageFailing
ErrorText : Exception calling "Invoke" with "0" argument(s): "The term 'Invoke-AsWorkflow' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was 
            included, verify that the path is correct and try again." System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "The term 'Invoke-AsWorkflow' is not recognized as the name 
            of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again." ---> System.Management.Automation.CommandNotFoundException: 
            The term 'Invoke-AsWorkflow' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.   
             at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at CallSite.Target(Closure , CallSite , Object )    --- End of inner 
            exception stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    at ExecuteInRunspace(Closure , FunctionContext )

Title     : ScriptCmdletUnderConstrainedLanguagePassing
Repro     : .\runlite -suite Scripting.CoreLanguage.CoreLanguageTest -pri  -test ScriptCmdletUnderConstrainedLanguagePassing
ErrorText : Exception calling "Invoke" with "0" argument(s): "The term 'Invoke-AsWorkflow' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was 
            included, verify that the path is correct and try again." System.Management.Automation.MethodInvocationException: Exception calling "Invoke" with "0" argument(s): "The term 'Invoke-AsWorkflow' is not recognized as the name 
            of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again." ---> System.Management.Automation.CommandNotFoundException: 
            The term 'Invoke-AsWorkflow' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.   
             at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)    at System.Management.Automation.Runspaces.Pipeline.Invoke()    at CallSite.Target(Closure , CallSite , Object )    --- End of inner 
            exception stack trace ---    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)    at ExecuteInRunspace(Closure , FunctionContext )

Title     : DRT - TestMonitorRunspaceInfo-0
Repro     : 
ErrorText : 

Title     : DRT - TestNestedDebuggerAPIs-0
Repro     : 
ErrorText : 

Title     : DRT - TestNestedStandaloneDebugger-0
Repro     : 
ErrorText : 

Title     : DRT - TestNestedEmbeddedDebugger-0
Repro     : 
ErrorText : 

Title     : DRT - TestRunspaceCollection-0
Repro     : 
ErrorText : 

Title     : TestMonitorRunspaceInfo-0
Repro     : .\runlite -suite PowerShellDebuggerUnitTests.RunspaceDebuggingTests -pri  -test TestMonitorRunspaceInfo-0
ErrorText : Test method PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestMonitorRunspaceInfo threw exception:  System.MethodAccessException: Attempt by method 
            'PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestMonitorRunspaceInfo()' to access method 'System.Management.Automation.Internal.PSMonitorRunspaceInfo.get_NestedDebugger()' failed.     at 
            PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestMonitorRunspaceInfo()       at PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestMonitorRunspaceInfo()

Title     : TestNestedDebuggerAPIs-0
Repro     : .\runlite -suite PowerShellDebuggerUnitTests.RunspaceDebuggingTests -pri  -test TestNestedDebuggerAPIs-0
ErrorText : Test method PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestNestedDebuggerAPIs threw exception:  System.MethodAccessException: Attempt by method 
            'PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestNestedDebuggerAPIs()' to access method 'System.Management.Automation.StandaloneRunspaceDebugger..ctor(System.Management.Automation.Runspaces.Runspace)' failed.     at 
            PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestNestedDebuggerAPIs()       at PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestNestedDebuggerAPIs()

Title     : TestNestedStandaloneDebugger-0
Repro     : .\runlite -suite PowerShellDebuggerUnitTests.RunspaceDebuggingTests -pri  -test TestNestedStandaloneDebugger-0
ErrorText : Test method PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestNestedStandaloneDebugger threw exception:  System.MethodAccessException: Attempt by method 
            'PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestNestedStandaloneDebugger()' to access method 'System.Management.Automation.Debugger.get_IsPushed()' failed.     at 
            PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestNestedStandaloneDebugger()       at PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestNestedStandaloneDebugger()

Title     : TestNestedEmbeddedDebugger-0
Repro     : .\runlite -suite PowerShellDebuggerUnitTests.RunspaceDebuggingTests -pri  -test TestNestedEmbeddedDebugger-0
ErrorText : Assert.IsTrue failed. FAIL: TestNestedEmbeddedDebugger: Expected nested debugger break all event to be received.    at PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestNestedEmbeddedDebugger()      at 
            PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestNestedEmbeddedDebugger()

Title     : TestRunspaceCollection-0
Repro     : .\runlite -suite PowerShellDebuggerUnitTests.RunspaceDebuggingTests -pri  -test TestRunspaceCollection-0
ErrorText : Test method PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestRunspaceCollection threw exception:  System.MethodAccessException: Attempt by method 
            'PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestRunspaceCollection()' to access method 'System.Management.Automation.Runspaces.Runspace.get_RunspaceDictionary()' failed.     at 
            PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestRunspaceCollection()       at PowerShellDebuggerUnitTests.RunspaceDebuggingTests.TestRunspaceCollection()

Title     : versioning
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: There were error records output from the script. Id: Microsoft.PowerShell.Commands.WriteErrorException,Assert, Id: ScriptHalted  ---> 
            Microsoft.PowerShell.Commands.WriteErrorException: Major build version of PowerShell should be 10    --- End of inner exception stack trace ---    at 
            Microsoft.Test.Management.Automation.ScriptTestFixture.ExecuteScriptFile(String scriptPath) Parameter 0: C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Language\versioning.ps1 Running script: 
            C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Language\versioning.ps1

Title     : TestFileSystemUNCPath
Repro     : C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\TTest.exe /log
ErrorText : Microsoft.VS.TTest.TestFailureException: There were error records output from the script. Id: NativeCommandError, Id: NativeCommandErrorMessage, Id: PathNotFound,Microsoft.PowerShell.Commands.SetLocationCommand, Id: 
            Microsoft.PowerShell.Commands.WriteErrorException,Assert, Id: ScriptHalted  ---> System.Management.Automation.RemoteException: This shared resource does not exist.    --- End of inner exception stack trace ---    at 
            Microsoft.Test.Management.Automation.ScriptTestFixture.ExecuteScriptFile(String scriptPath) Parameter 0: C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Namespaces\TestFileSystemUNCPath.ps1 Running script: 
            C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Namespaces\TestFileSystemUNCPath.ps1
@vors

This comment has been minimized.

Collaborator

vors commented Feb 13, 2016

Name

TestGetFormatDataAndExportFormatData

File

C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Commands\TestGetFormatDataAndExportFormatData.ps1

Repro

(Get-FormatData System.Diagnostics.Process).FormatViewDefinition.Count

Expected

4

Actual

2

Issue file for failure: #1278

@vors

This comment has been minimized.

Collaborator

vors commented Feb 13, 2016

Name

  • winblue_71908_HelpInfoUriForRemoteModule
  • remoteDiscovery-psSession-cimModule
  • remoteDiscovery-psSession-psModule

Missing cmdlets

Cmdlets Import-PSSession and Export-PSSession are missing, it's a known issue (ImplicitRemotingCommands.cs)

@vors

This comment has been minimized.

Collaborator

vors commented Feb 13, 2016

CmsMessageCommandsCore

Cmdlet Protect-CmsMessage is missing from Microsoft.PowerShell.Security

MessageRecipientByCert

Cmdlet Get-PfxCertificate is missing from Microsoft.PowerShell.Security

@vors

This comment has been minimized.

Collaborator

vors commented Feb 13, 2016

all workflow

Including

  • InvokeScriptWithRequiresModule
  • AliasAttributeTestForCmdletAdvFnAndWorkflow

I messed up with install script and removed psworkflow module, please ignore these errors

@vors

This comment has been minimized.

Collaborator

vors commented Feb 13, 2016

Followup.Tests

it's a problem with tests caused by CL 677290 and fixed in CL 679824

@vors

This comment has been minimized.

Collaborator

vors commented Feb 13, 2016

Name

winblue_191746_DSCModulePath

File

C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Modules\winblue_191746_DSCModulePath.ps1

Repro

  • It would not work if you run powershell side-by-side with Start-DevPSGithub, because process inherits$env:PSModulePath
$env:PSModulePath -match "Program Files\\WindowsPowerShell\\Modules"

Expected

True

Actual

False

@vors

This comment has been minimized.

Collaborator

vors commented Feb 13, 2016

Name

TestNewPSDriveWithCredential

File

C:\PowerShellTests\PowerShell\Win8\PowerShell\legacy\utscripts\Security\TestNewPSDriveWithCredential.ps1

Repro

Sorry, repro is quite big, but I could not make it significantly smaller.

Save this is a script and run it in an elevated powershell

try
{

    # Create a new temporary user account and add it to the list of administrators.
    # This account would be deleted as part of the cleanup process.
    net user /add fileShareUser C1~eeFileShare | Out-NUll

    # Fetch localized name for administrators group.
    $identifier = new-object System.Security.Principal.SecurityIdentifier([System.Security.Principal.WellKnownSidType]"BuiltinAdministratorsSid", $null)  
    $ntAccountWithDomain = $identifier.Translate([System.Security.Principal.NTAccount])  
    $localizedGroupName = $ntAccountWithDomain.Value.split("\\")[1]
    net localgroup $localizedGroupName fileShareUser /add  | Out-NUll


    $computerName = $env:Computername
    $username2 = "$computerName\fileShareUser2"
    $password2 = ConvertTo-SecureString -AsPlainText "C1~eeFile" -Force
    $cred2 = New-Object System.Management.Automation.PSCredential $username2,$password2
    net user /add fileShareUser2 C1~eeFile  | Out-NUll

    $tempDir = $env:SystemDrive

    $share = "\\$computerName\TestNetworkPSDrive"

    New-Item $tempDir\TestNetworkPSDrive -Type Directory | Out-Null
    net share TestNetworkPSDrive=$tempDir\TestNetworkPSDrive /grant:'fileShareUser,full' | Out-NUll

    New-Item $tempDir\TestNetworkPSDrive\Source -Type Directory | Out-Null
    New-Item $tempDir\TestNetworkPSDrive\Source\TestFile.txt -Type File | Out-Null


    $newDrive2 = New-PSDrive -Name TestDriveForFileSystemCredentials2 -Root $share -PSProvider FileSystem -Credential $cred2 
    if ($newDrive2)
    {
        Write-Host "Success"
    }
    else
    {
        Write-Host "Failed to create PSDrive"
    }

    # The PSDrive "TestDriveForFileSystemCredentials2" is created with "fileShareUser2" user credentials which does not have access to the share.
    # Hence when ever an attempt is made to access this "TestDriveForFileSystemCredentials2" PSDrive, an "Access Denied exception woudl be thrown.
    # This is a negative test case to make sure that if a PSDrive is created on a local share with user credentials that dont have access to the share, 
    # and operation on such a drive would result in "Acccess Denied" error.
    Get-ChildItem TestDriveForFileSystemCredentials2:\  -ErrorAction SilentlyContinue -ErrorVariable ev

    # Deleting the PSDrive "TestDriveForFileSystemCredentials2" as its no longer required.
    # This will delete the connection established to PSDrive "TestDriveForFileSystemCredentials2"
    Remove-PSDrive -Name TestDriveForFileSystemCredentials2  | Out-NUll

}
finally 
{
    # Clean Up activity.
    net share TestNetworkPSDrive \\$computerName /DELETE /Y | Out-NUll
    Remove-Item -Path $tempDir\TestNetworkPSDrive -Force -Recurse -ErrorAction SilentlyContinue | Out-NUll
    net user /delete fileShareUser | Out-NUll
    net user /delete fileShareUser2 | Out-NUll
}

Expected

Success

Actual

New-PSDrive : The specified drive root "\\VSBOX\TestNetworkPSDrive" either
does not exist, or it is not a folder.
At D:\junk\psdrive.ps1:32 char:18
+ ... newDrive2 = New-PSDrive -Name TestDriveForFileSystemCredentials2 -Roo ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ReadError: (TestDriveForFileSystemCredentials2:P
   SDriveInfo) [New-PSDrive], IOException
    + FullyQualifiedErrorId : DriveRootError,Microsoft.PowerShell.Commands.New
   PSDriveCommand

Failed to create PSDrive
Remove-PSDrive : Cannot find drive. A drive with the name
'TestDriveForFileSystemCredentials2' does not exist.
At D:\junk\psdrive.ps1:50 char:5
+     Remove-PSDrive -Name TestDriveForFileSystemCredentials2  | Out-NU ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (TestDriveForFileSystemCredentia
   ls2:String) [Remove-PSDrive], DriveNotFoundException
    + FullyQualifiedErrorId : DriveNotFound,Microsoft.PowerShell.Commands.Remo
   vePSDriveCommand
@vors

This comment has been minimized.

Collaborator

vors commented Feb 18, 2016

Update: I did a run with changes from #554 and result is little bit better.
Still cannot figure what part of Update-PSCore.cmd removes psworkflow module

BVT: total=500 Pass=497 Fail=3 Error=0 Skip=0 Unspecified=0 Blocked=0 
DRT: total=3238 Pass=3164 Fail=53 Error=1 Skip=6 Unspecified=14 Blocked=0 
P0: total=5881 Pass=5717 Fail=78 Error=0 Skip=72 Unspecified=0 Blocked=14 
@andschwa

This comment has been minimized.

Member

andschwa commented Feb 18, 2016

Awesome to see 😄

@vors vors removed their assignment Feb 19, 2016

@vors vors added the BVT/DRT label Feb 20, 2016

@vors

This comment has been minimized.

Collaborator

vors commented Feb 20, 2016

Made another run with the right version of Update-PSCore.cmd (which doesn't replace powershell.exe and doesn't remove psworkflow module). Got even better results 👯

BVT: total=500 Pass=500 Fail=0 Skip=0 Unspecified=0 Blocked=0 
DRT: total=3238 Pass=3186 Fail=32 Skip=6 Unspecified=14 Blocked=0 
P0: total=6244 Pass=6112 Fail=46 Skip=72 Unspecified=0 Blocked=14 
@andschwa

This comment has been minimized.

Member

andschwa commented Feb 20, 2016

Sweet!

@andschwa

This comment has been minimized.

Member

andschwa commented Feb 22, 2016

@andschwa

This comment has been minimized.

Member

andschwa commented Mar 1, 2016

@vors What do we need to do to move forward now?

@vors

This comment has been minimized.

Collaborator

vors commented Mar 1, 2016

  1. Address issues that I already identified (probably create separate bugs for them)
  2. After that, make a new run. Instruction is available here https://github.com/PowerShell/Internal-PowerShellTeam-Tools/blob/master/PowerShellDevelopersWiki/Workflow.md#testing

You should be able to work on it without my help. but I'm happy to assist if needed.

@vors

This comment has been minimized.

Collaborator

vors commented Mar 1, 2016

Use matching versions of VMQuick (or vhd, if you don't like VMQuick) and tests that you are deploying. Also, I always run tests on two machines: one clean, one with my changes. The first one helps to ignore some failures, that not caused by your changes.

@andschwa also, do you want me to update source-depot branch?

@andschwa

This comment has been minimized.

Member

andschwa commented Mar 1, 2016

How do I know what version of VMQuick and tests to use?

@vors

This comment has been minimized.

Collaborator

vors commented Mar 1, 2016

Go to VMQuick, get the last available one from nebula from rs1_srv_ps_dev branch.
I.e. 14272.1000.amd64fre.rs1_srv_ps_dev.160226-1500_server_serverdatacenter_en-us.vhd the important part is 160226

Then find a corresponding build folder on \\winbuilds\release\rs1_srv_ps_dev, in this case it's 14272.1000.160226-1500. This is the $build from

$build = '14257.1000.160201-1500'
$admin = "\\winbuilds\release\rs1_srv_ps_dev\$build\amd64fre\bin\admin"
& $admin\admintest\ci\InstallProject.ps1 -ProjectFilePath "$admin\admintest\ci\Project.PowerShell.xml" -targetDirectory "c:\PowerShellTests\"

UPD: You can get the same string with concatenating two substrings from vhd name as well. (I just never did it for some reason)

@andschwa

This comment has been minimized.

Member

andschwa commented Mar 1, 2016

Thanks, I will start this tomorrow and see where I get 😄

@andschwa andschwa self-assigned this Mar 1, 2016

@vors

This comment has been minimized.

Collaborator

vors commented Mar 2, 2016

@andschwa

This comment has been minimized.

Member

andschwa commented Mar 5, 2016

We've got the source depot changes merged, I will take care of this right after v0.2.0 (which I want for Tuesday's demo). I should be able to plow through quite a few M/T/W, but will be OOF T/F due to multiple wisdom teeth getting removed 🔧.

@andschwa andschwa added this to the Preview 1 milestone Mar 5, 2016

@andschwa andschwa modified the milestones: Preview 1+, Preview 1 Mar 28, 2016

@vors vors referenced this issue Apr 12, 2016

Closed

Parity with windows dev workflow (aka move to github) #824

10 of 13 tasks complete
@andschwa

This comment has been minimized.

Member

andschwa commented Apr 14, 2016

Update on this:

Since @JumpingYang001, @TingLiu6, and @brycem are porting the BVT/DRT tests to Open PowerShell, it's going to be much easier to fix the BVT/DRTs as failures are found during porting, since they're immediately reproducible with local tests and CI (in contrast to spinning up a separate test VM and having to deploy new bits for every attempted repro).

So our current plan is to do that until the test porting is done, and then afterward re-run it through the old system to ensure nothing was missed.

/cc @paulcallen

@andschwa andschwa modified the milestones: Preview 1+, RTM Apr 14, 2016

@andschwa andschwa added the Issue-Meta label Apr 21, 2016

@vors

This comment has been minimized.

Collaborator

vors commented May 13, 2016

Today's results

BVT: total=493 Pass=487 Fail=6 Error=0 Skip=0 Unspecified=0 Blocked=0 
DRT: total=2745 Pass=2598 Fail=116 Error=11 Skip=6 Unspecified=14 Blocked=0 
P0: total=5895 Pass=5595 Fail=206 Error=9 Skip=71 Unspecified=0 Blocked=14

:(

@andschwa

This comment has been minimized.

Member

andschwa commented May 13, 2016

What are the failures?

@vors

This comment has been minimized.

Collaborator

vors commented May 13, 2016

Here is the list, I send more detailed log in an email, becasue it's too big

NewFileCatalogFolder-0
NewFileCatalogFolderWithSubFolders-0
NewFileCatalogWithSingleFile-0
NewFileCatalogForFilesThatDoNotSupportEmbeddedSignatures-0
NewFileCatalogMultipleFilesSameRoot-0
NewFileCatalogWithMutipleFoldersAndFiles-0
NewFileCatalogVersion2WithMutipleFoldersAndFiles-0
NewAndTestFileSignedCatalog-0
NewFileCatalogFolderWhenCatlogFileIsCreatedInsideSameFolder-0
NewFileCatalogWithUnicodeCharactersInFileNames-0
TestCatalogWhenNewFileAddedtoFolderBeforeValidation-0
TestCatalogWhenNewFileDeletedFromFolderBeforeValidation-0
TestCatalogWhenFileContentModifiedBeforeValidation-0
TestCatalogWhenFileRenamedBeforeValidation-0
TestCatalogWhenFolderRenamedBeforeValidation-0
TestCatalogWhenFileRelativePathChangedBeforeValidation-0
NewFileCatalogDuplicateRelativePaths-0
TestFileCatalogDuplicateRelativePaths-0
NewFileCatalogUnknownVersion-0
TestCatalogSkipSingleFileDuringValidation-0
TestCatalogSkipCertainFileTypeDuringValidation-0
TestCatalogSkipWildCardPatternDuringValidation-0
TestCatalogSkipMuitplePattensDuringValidation-0
Changes first and last name with one Example-0
Changes first and last name with one Example, and three inputs-0
Changes first and last name with two Examples-0
Changes first and last name with one dictionary example-0
Changes first and last name with two dictionary example-0
Replace by empty-0
verifies automatic property generation-0
verifies property overflow generation-0
verifies property renaming-0
verifies property typing of numbers-0
verifies property typing of TimeSpan-0
verifies property typing of DateTime-0
verifies property typing of Char-0
verifies empty strings don't turn into INTs-0
verifies property typing of String-0
verifies the ability to change the delimiter-0
verifies that only matching text gets parsed-0
verifies that a good error message is returned from an invalid regular expression-0
Tests Invoke-History on a cmdlet that generates output on all streams-0
ShouldNotHaveV2
Value1AndValue2NotBothNull
MeasureTextCombinationTest
TestGetFormatDataAndExportFormatData
TestCase1
InvokeHistoryLastEntry
SuiteSetupOrCleanUpFailure
Test-ISS-CreateDefault2
GetResourceStringTest
UpdateHelpWhatIf
LoggerUnfoldArray-0
ModuleEnhancementForOperateCoreModule-0
AliasAttributeTestForCmdletAdvFnAndWorkflow-0
Verifies Information stream on workflow-0
Verifies InformationVariable in workflow compilation-0
GenericExceptionTest1
SuiteSetupOrCleanUpFailure
GetMshSnapinBlankNoParameterTestNoMshSnapinsLoaded
SuiteSetupOrCleanUpFailure
SuiteSetupOrCleanUpFailure
SuiteSetupOrCleanUpFailure
SuiteSetupOrCleanUpFailure
SuiteSetupOrCleanUpFailure
winblue_121450
PassingRefToNonRef
PassingNonRefToRefandOut
remoteDiscovery-cimSession-bug769014
remoteDiscovery-cimSession-cimModule
remoteDiscovery-cimSession-mixedModule
remoteDiscovery-psSession-cimModule
TestCmdletDefinitionSigning
TestNewPSDriveWithCredential
bug-win8-134523-tooMuchPositionalBinding
bug-win8-138600-createInstanceAndKeys
bug-win8-144782-modifyInstanceAndNewValuesFromInputObject
bug-win8-145006-duplicateClientSideVerboseMsg
bug-win8-145681-switchParametrerAsMethodParameter
bug-win8-162870-childJobsHaveResults
bug-win8-164685-caseInsensitivityOfCharAndString
bug-win8-167425-blockingEnumerator
bug-win8-169347-errorWhenAssociationQueryDoesntReturnAnything
bug-win8-169371-invocationInfoInErrors
bug-win8-201853-errorsFromEnumRelatedAddType
bug-win8-225318-suppressingOfPassThruProcessing
bug-win8-232409-crashWhenErrorInOnNext
bug-win8-239206-arrayOfEnums
bug-win8-241907-specialCharactersInEnumIdentifiers
bug-win8-265424-opopt-vs-paramsets
bug-win8-274981-streaming-vs-regularResult
bug-win8-387140-enumerateInsteadOfWql
bug-win8-413565-cdxmlFlagToControlNotFoundErrors
bug-win8-453462-nestedModulesVSrootCdxmlModule
bug-win8-456908-parameterSetsForSameMethod
bug-win8-483744-workflowCompilationWithRequiredCimModule
bug-win8-489202-noSupportForShouldProcessInRemoteDcom
bug-win8-528933-etsTypeStampingDoesntIntroduceDuplicates
bug-win8-528933-stampingEtsTypeOnCmdletOutput
bug-win8-538441-psshowcomputername
bug-win8-60920-createModifyPassThru
bug-win8-625700-interop-resourceUri
bug-win8-645771-objNotFound-intVsEnum
bug-win8-713939-noRtti-vs-intQueryableProperty
bug-winblue-119609-secureString
e2e-assoc
e2e-extSem-debug
e2e-extSem-error
e2e-extSem-progress
e2e-extSem-shouldProces
e2e-extSem-verbose
e2e-extSem-warning
e2e-help
e2e-inst-deleteInstance
e2e-inst
e2e-operationOptions
e2e-outParameterStreaming
e2e-passthru
e2e-query-notFound
e2e-query
e2e-serialization
e2e-session-stickyness
e2e-shouldProcess-clientSide-deleteInstance
e2e-shouldProcess-clientSide-inst
e2e-stat
xsd-cmdletmetadata
xsd-cmdletparams-positionOrder
xsd-cmdletparams-pscredential
xsd-cmdletparams-pstypename
xsd-cmdletparams
xsd-empty
xsd-enums
xsd-inst-1param2psets
xsd-inst-defpset
xsd-inst-getcmdletoverride
xsd-inst-getparamsoverride
xsd-inst-queryTypes
xsd-inst
xsd-outparams
xsd-outputTypeAttribute
xsd-outputTypeAttribute2
xsd-passthru
xsd-privatedata
xsd-stat-1param2psets
xsd-stat-defpset
xsd-stat
xsd-validation
DefaultPromptingExceptionCtorTest
ExposeBug921858
GetPSDriveDetectsNetworkMappedDrive
RemoveNetworkMappedDrive
SuiteSetupOrCleanUpFailure
PowerShellTranscriptionCapturesNativeExes
ExposeSetLocationUNCProviderQualifiedPathBug
ExposeSetLocationUNCDirectPathBug
ClearContent
GetContent
GetItem
GetItemMultipleStreams
RemoveItem
SetContent
System.Management.Automation.Remoting.UnitTests.WSManPluginEntryDelegatesUnitTests.ConstructionCreatesDelegates
System.Management.Automation.Remoting.UnitTests.WSManPluginEntryDelegatesUnitTests.InitPluginAssignsWorkerPtrs
System.Management.Automation.Remoting.UnitTests.WSManPluginEntryDelegatesUnitTests.NullInputIsNoOp
System.Management.Automation.Remoting.UnitTests.WSManPluginShellSessionUnitTests.CloseCommandOperationDoesNothingIfUnmatchedContext
System.Management.Automation.Remoting.UnitTests.WSManPluginShellSessionUnitTests.GetCommandSessionReturnsNullIfNoCommandSession
DRT - TestCreateProcessPipeName-0
DRT - TestCreateNamedPipeServer-0
DRT - TestCreateNamedPipeClient-0
DRT - TestCreateContainerNamedPipeClient-0
DRT - TestClientServerConnect-0
DRT - TestNamedPipeDuplicateServerPipe-0
DRT - TestNamedPipeClientSessionTransportManager-0
TestCreateProcessPipeName-0
TestCreateNamedPipeServer-0
TestCreateNamedPipeClient-0
TestCreateContainerNamedPipeClient-0
TestClientServerConnect-0
TestNamedPipeDuplicateServerPipe-0
TestNamedPipeClientSessionTransportManager-0
ActivityWithScriptBlock
WorkflowFullLanguage
CIMCmdletUnderConstrainedLanguage
DefaultExecutionContextSessionStateLanguageModeInRemoteSession
ScriptCmdletUnderConstrainedLanguageFailing
ScriptCmdletUnderConstrainedLanguagePassing
DRT - TestMonitorRunspaceInfo-0
DRT - TestNestedDebuggerAPIs-0
DRT - TestNestedStandaloneDebugger-0
DRT - TestNestedEmbeddedDebugger-0
DRT - TestRunspaceCollection-0
TestMonitorRunspaceInfo-0
TestNestedDebuggerAPIs-0
TestNestedStandaloneDebugger-0
TestNestedEmbeddedDebugger-0
TestRunspaceCollection-0
actionpreference
versioning
SuiteSetupOrCleanUpFailure
TestFileSystemUNCPath

@andschwa

This comment has been minimized.

Member

andschwa commented May 13, 2016

I see a couple themes here:

Missing cmdlets, at least one which I'm sure comes from the file that hasn't been compiled into SMA yet.

Unfound resources, since the names of the resources are different in PS with CLI than with Razzle, and the FullCLR build doesn't have all the assemblies the tests use. Thus it shares with assemblies built by Razzle, and so look for resources under a different name.

To eliminate build differences (which will exist until the rest of PS for FullCLR is ported), the tests need to be run on a build where our changes and additional file are applied to SD. I don't think mixing assemblies will yield accurate results. This would probably get us back to our February results.

Also I assumed this was for the FullCLR build. We need to see a CoreCLR set as well, with the same build caveats.

@vors

This comment has been minimized.

Collaborator

vors commented May 13, 2016

Applying source can help in eliminating noise, but it doesn't bring us closer to the end goal, since we don't plan to checking OpenPS code into sd.

I think it's more valuable to start building all the necessary assemblies to bridge the gap.

@andschwa

This comment has been minimized.

Member

andschwa commented May 13, 2016

I agree completely, that's the best solution. We'll have a lot of test noise until then, and that's probably okay.

Getting everything built wil also codify the differences among the flavors' dependencies, which is information we need anyway.

@HemantMahawar HemantMahawar modified the milestones: Aug17, Future Jul 20, 2016

@vors vors removed the cut-aug17 label Jul 21, 2016

@hiteshraigandhi hiteshraigandhi modified the milestones: Future, 6.0.0-Alpha.10 Jul 28, 2016

@adityapatwardhan

This comment has been minimized.

Member

adityapatwardhan commented Jul 29, 2016

Individual issues have been filed for BVT/DRT failures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment