release/v7.4.8_package_references_30cb914bc-b8def95fb - 51 #51
windows-ci.yml
on: push
Change Detection
14s
Windows Unelevated CI
22m 4s
Windows Elevated CI
7m 32s
Windows Unelevated Others
21m 33s
Windows Elevated Others
12m 14s
Verify xUnit test results
26s
windows ready to merge
/
all jobs passed
4s
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:df7847dea2bdbe1774961ff522eaf48872a74221a0d4ff1b275c8f1a87ba253c
|
|
|
ctrf-pester-ElevatedPesterTests-CI
|
6.57 KB |
sha256:29d063475cfb5283d5516296cf6050690b80b2f7a3c443e5fc03ce14ef7ad23e
|
|
|
ctrf-pester-ElevatedPesterTests-Others
|
27.9 KB |
sha256:a3378ff7eb52f62ef1c19621f33800f5c638daee7d1fcba3d111381975c8a742
|
|
|
ctrf-pester-UnelevatedPesterTests-CI
|
163 KB |
sha256:aaef7e2da581860943d6a7cd35605759f2dc309730ab164dea5555ecc8d1371e
|
|
|
ctrf-pester-UnelevatedPesterTests-Others
|
30.9 KB |
sha256:63c856f3dd575864e1bb6df23b90784684bb330f35fa3dcb132a246aea2c18ba
|
|
|
junit-pester-ElevatedPesterTests-CI
|
18.2 KB |
sha256:c997720b576107a8f63408093481e37de7ed974c98294d6f9b7f15e448630519
|
|
|
junit-pester-ElevatedPesterTests-Others
|
40.3 KB |
sha256:7dd226abb9afb7cac824b6dab92f31683ba5442a366e2102af8379a232ae9afd
|
|
|
junit-pester-UnelevatedPesterTests-CI
|
175 KB |
sha256:a296842304062a099e369debf7dcad284c7e29aab5161e36bb760e9cc9c74792
|
|
|
junit-pester-UnelevatedPesterTests-Others
|
42.6 KB |
sha256:a14beb1cae4df4c881426e097fca82c5ac9e3187affebe6d0596cc0721b08ef9
|
|
|
testResults-xunit
|
6.01 KB |
sha256:15d9cb5c539242a1674d281d8ed30e04b245f55f0f80ae69c1a5f3e348ec5e01
|
|