Skip to content

Fix #2649: Catch ToString() exceptions in NUnit3 output #2697

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.

Sign up for GitHub

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

Open
nohwnd wants to merge 1 commit into
base: main
Choose a base branch
from
+52 −1

Fix #2649: Catch ToString() exceptions in NUnit3 output

d19716e
Select commit
Loading
Failed to load commit list.
Open

Fix #2649: Catch ToString() exceptions in NUnit3 output #2697

Fix #2649: Catch ToString() exceptions in NUnit3 output
d19716e
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Pester PR failed Apr 3, 2026 in 9m 48s

Build #20260403.22 had test failures

11 errors / 0 warnings

Details

Tests

  • Failed: 1 (0.01%)
  • Passed: 17,167 (98.21%)
  • Other: 312 (1.78%)
  • Total: 17,480
Code coverage

  • 6335 of 7228 line covered (87.65%)

Annotations

Check failure on line 3252 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L3252 

 [-] <ScriptBlock> failed with:

Check failure on line 3942 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L3942 

 [-] Should-BeFasterThan.Has Because parameter 3ms (2ms|1ms)

Check failure on line 3971 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L3971 

PowerShell exited with code '1'.

Check failure on line 3211 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Build log #L3211 

 [-] <ScriptBlock> failed with:

Check failure on line 1 in Should-BeFasterThan.Has Because parameter("1ms","I said so", Start-Sleep -Milliseconds 10 )

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR

Should-BeFasterThan.Has Because parameter("1ms","I said so", Start-Sleep -Milliseconds 10 ) 

Exception: Expected the script block {  $Actual | Should-BeFasterThan -Expected $Expected -Because $Because  } to fail in Pester assertion, but no assertion failure error was thrown!
Raw output 
at Verify-AssertionFailed, D:\a\1\s\tst\axiom\Verify-AssertionFailed.ps1:26
at <ScriptBlock>, D:\a\1\s\tst\functions\assert\Time\Should-BeFasterThan.Tests.ps1:54
View more details on Azure Pipelines