WIP: add more detail to suspicious scriptblock logging #21475
Closed
Azure Pipelines / PowerShell-CI-windows
failed
Apr 16, 2024 in 33m 17s
Build #PR-21475-20240416.01 had test failures
Details
- Failed: 2 (0.01%)
- Passed: 12,816 (94.19%)
- Other: 789 (5.80%)
- Total: 13,607
Annotations
Check failure on line 855 in Build log
azure-pipelines / PowerShell-CI-windows
Build log #L855
PowerShell exited with code '1'.
Check failure on line 862 in Build log
azure-pipelines / PowerShell-CI-windows
Build log #L862
There are one or more test failures detected in result files. Detailed summary of published test results can be viewed in the Tests tab.
azure-pipelines / PowerShell-CI-windows
Basic EventLog tests on Windows.Verifies scriptblock logging: normal script block
Expected strings to be the same, but they were different.
Expected length: 54
Actual length: 73
Strings differ at index 0.
Expected: 'Write-Verb...'
But was: 'Detected t...'
Raw output
at <ScriptBlock>, D:\a\1\s\test\powershell\Host\Logging.Tests.ps1: line 498
498: $created.Properties[2].Value | Should -Be $expectedText
azure-pipelines / PowerShell-CI-windows
Basic EventLog tests on Windows.Verifies scriptblock logging: script block with Null
Expected strings to be the same, but they were different.
Expected length: 55
Actual length: 74
Strings differ at index 0.
Expected: 'Write-Verb...'
But was: 'Detected t...'
Raw output
at <ScriptBlock>, D:\a\1\s\test\powershell\Host\Logging.Tests.ps1: line 498
498: $created.Properties[2].Value | Should -Be $expectedText