Skip to content

Fix #2561: Escape control characters in assertion error messages #2690

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

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

Fix #2561: Escape control characters in assertion error messages

1d213ef
Select commit
Loading
Failed to load commit list.
Draft

Fix #2561: Escape control characters in assertion error messages #2690

Fix #2561: Escape control characters in assertion error messages
1d213ef
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Pester PR (Test PS7_Windows_Server2022) failed Apr 3, 2026 in 3m 14s

Test PS7_Windows_Server2022 failed

4 errors / 0 warnings

Annotations

Check failure on line 22 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR (Test PS7_Windows_Server2022)

Build log #L22 

There are one or more test failures detected in result files. Detailed summary of published test results can be viewed in the Tests tab.

Check failure on line 3252 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR (Test PS7_Windows_Server2022)

Build log #L3252 

 [-] <ScriptBlock> failed with:

Check failure on line 3940 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR (Test PS7_Windows_Server2022)

Build log #L3940 

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

Check failure on line 3969 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR (Test PS7_Windows_Server2022)

Build log #L3969 

PowerShell exited with code '1'.
View more details on Azure Pipelines