Skip to content

release/v7.4.8_package_references_30cb914bc-422ae2d40 - 50 #50

release/v7.4.8_package_references_30cb914bc-422ae2d40 - 50

release/v7.4.8_package_references_30cb914bc-422ae2d40 - 50 #50

Triggered via push April 2, 2026 14:25
Status Failure
Total duration 30m 28s
Artifacts 10

windows-ci.yml

on: push
Change Detection
17s
Change Detection
Build PowerShell
5m 6s
Build PowerShell
Windows Unelevated CI
24m 43s
Windows Unelevated CI
Windows Elevated CI
7m 37s
Windows Elevated CI
Windows Unelevated Others
16m 43s
Windows Unelevated Others
Windows Elevated Others
8m 42s
Windows Elevated Others
Verify xUnit test results
25s
Verify xUnit test results
windows ready to merge  /  all jobs passed
3s
windows ready to merge / all jobs passed
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 7 warnings
Windows Elevated Others
Github Test Reporter: 7 failed tests found
Failed Test: D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageRestriction.Tests.ps1: Dot sourced script block functions from trusted script files should not run FullLanguage in ConstrainedLanguage context.Verifies a scriptblock from a trusted script file does not run as trusted
D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageRestriction.Tests.ps1: Dot sourced script block functions from trusted script files should not run FullLanguage in ConstrainedLanguage context.Verifies a scriptblock from a trusted script file does not run as trusted: The term 'RunScriptBlock' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. - No trace available
Failed Test: D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: New-Module should not create module from trusted scriptblock when running in ConstrainedLanguage context.New-Module succeeds in creating module with untrusted scriptblock in ConstrainedLanguage
D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: New-Module should not create module from trusted scriptblock when running in ConstrainedLanguage context.New-Module succeeds in creating module with untrusted scriptblock in ConstrainedLanguage: Cannot create new module while the session is in ConstrainedLanguage mode. - No trace available
Failed Test: D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: Untrusted manifest and module files import in lock down mode.Verifies that importing untrusted module file in lock down mode exports all functions by default
D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: Untrusted manifest and module files import in lock down mode.Verifies that importing untrusted module file in lock down mode exports all functions by default: Expected 2, but got 0. - No trace available
Failed Test: D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: Untrusted manifest and module files import in lock down mode.Verifies that importing untrusted manifest in lock down mode exports all functions by default
D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: Untrusted manifest and module files import in lock down mode.Verifies that importing untrusted manifest in lock down mode exports all functions by default: Expected 2, but got 0. - No trace available
Failed Test: D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: Import mix of trusted and untrusted manifest and module files.Verifies that an untrusted manifest containing all trusted modules does not load under system lock down
D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: Import mix of trusted and untrusted manifest and module files.Verifies that an untrusted manifest containing all trusted modules does not load under system lock down: Expected strings to be the same, but they were different. Expected length: 81 Actual length: 13 Strings differ at index 0. Expected: 'Modules_Mi...' But was: 'No Exception!' - No trace available
Failed Test: D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: Import mix of trusted and untrusted manifest and module files.Verifies that an untrusted module with nested trusted modules cannot load in a locked down system
D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: Import mix of trusted and untrusted manifest and module files.Verifies that an untrusted module with nested trusted modules cannot load in a locked down system: Expected strings to be the same, but they were different. Expected length: 81 Actual length: 13 Strings differ at index 0. Expected: 'Modules_Mi...' But was: 'No Exception!' - No trace available
Failed Test: D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: Import mix of trusted and untrusted manifest and module files.Verifies that an untrusted manifest with a trusted module will not load under system lockdown
D:\a\PowerShell\PowerShell\test\powershell\Modules\Microsoft.PowerShell.Security\ConstrainedLanguageModules.Tests.ps1: Import mix of trusted and untrusted manifest and module files.Verifies that an untrusted manifest with a trusted module will not load under system lockdown: Expected strings to be the same, but they were different. Expected length: 81 Actual length: 13 Strings differ at index 0. Expected: 'Modules_Mi...' But was: 'No Exception!' - No trace available
Windows Unelevated Others
Github Test Reporter: 3 failed tests found
Failed Test: D:\a\PowerShell\PowerShell\test\powershell\Host\ConsoleHost.Tests.ps1: WindowStyle argument.-WindowStyle Maximized should work on Windows
D:\a\PowerShell\PowerShell\test\powershell\Host\ConsoleHost.Tests.ps1: WindowStyle argument.-WindowStyle Maximized should work on Windows: Expected exactly 'Maximized', but got Hidden. - No trace available
Failed Test: D:\a\PowerShell\PowerShell\test\powershell\Host\ConsoleHost.Tests.ps1: WindowStyle argument.-WindowStyle Minimized should work on Windows
D:\a\PowerShell\PowerShell\test\powershell\Host\ConsoleHost.Tests.ps1: WindowStyle argument.-WindowStyle Minimized should work on Windows: Expected exactly 'Minimized', but got Hidden. - No trace available
Failed Test: D:\a\PowerShell\PowerShell\test\powershell\Host\ConsoleHost.Tests.ps1: WindowStyle argument.-WindowStyle Normal should work on Windows
D:\a\PowerShell\PowerShell\test\powershell\Host\ConsoleHost.Tests.ps1: WindowStyle argument.-WindowStyle Normal should work on Windows: Expected exactly 'Normal', but got Hidden. - No trace available
windows ready to merge / all jobs passed
Process completed with exit code 1.
Change Detection
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.0, dorny/paths-filter@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build PowerShell
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.0, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Verify xUnit test results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.0, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows Elevated CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.0, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows Elevated Others
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.0, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows Unelevated Others
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.0, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows Unelevated CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.0, actions/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
build
112 MB
sha256:0ae09588942d72b87602aeebbf564b4eb8cd46ce8e7510387e67cda6b91978a6
ctrf-pester-ElevatedPesterTests-CI
6.56 KB
sha256:ddf2a7396f80790a9d992618daa8eb8baa71cb0dfe8111def480e30bf1c43603
ctrf-pester-ElevatedPesterTests-Others
27.8 KB
sha256:8061ac4070db52ac28c24cbcd0ee1e8ca9934c97ea3c88e5888cb0d3cf6a49d3
ctrf-pester-UnelevatedPesterTests-CI
162 KB
sha256:2e0561b4b385afcac6ff4bd7a48ad03cc30c63626fbcccf96187cd74ba4df7f7
ctrf-pester-UnelevatedPesterTests-Others
30.7 KB
sha256:5a1883511ec4cadc7326c4b36f8835e426a437e2157cf624ffdf192aedb8fe67
junit-pester-ElevatedPesterTests-CI
18.2 KB
sha256:273e670f96bd7ed08bb81240339cca6b5d2c2ae351a18d15bf95ef0b53ac92e1
junit-pester-ElevatedPesterTests-Others
40.3 KB
sha256:1265b43e76fcc2fb7e1cbcd345cb81ab545fc47b1f7217e36b0aa1758f1b022b
junit-pester-UnelevatedPesterTests-CI
176 KB
sha256:2df1fef3432941fe5b96740d97b32bc726846d2276fd583e06add179c8e99a7d
junit-pester-UnelevatedPesterTests-Others
42.3 KB
sha256:19a22fd0991b2c78a9868903b0fdcd97c2665b62c3cf845a2537c2786f7514b1
testResults-xunit
6.03 KB
sha256:acaeef729072bb3e0cc9f5bc5d8f68782aa66c39411fe3ae3162e78a1cd63af2