Description
==> windows-2025-vs2026.azure-arm.image: Invoke-PesterTests : Unable to find type [PesterConfiguration].
==> windows-2025-vs2026.azure-arm.image: At C:\Windows\Temp\script-69d3d4be-a53b-cd3f-3aa2-efa7e92eb6d8.ps1:58 char:1
==> windows-2025-vs2026.azure-arm.image: + Invoke-PesterTests -TestFile "Docker" -TestName "Docker"
==> windows-2025-vs2026.azure-arm.image: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> windows-2025-vs2026.azure-arm.image: + CategoryInfo : InvalidOperation: (PesterConfiguration:TypeName) [Invoke-PesterTests], RuntimeException
==> windows-2025-vs2026.azure-arm.image: + FullyQualifiedErrorId : TypeNotFound,Invoke-PesterTests
==> windows-2025-vs2026.azure-arm.image:
==> windows-2025-vs2026.azure-arm.image: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]
==> windows-2025-vs2026.azure-arm.image: Step "StepProvision" failed
Platforms affected
Runner images affected
Image version and build link
Generating new image
Is it regression?
na
Expected behavior
Scheduled task should be created and executed successfully.
Actual behavior
==> windows-2025-vs2026.azure-arm.image: Invoke-PesterTests : Unable to find type [PesterConfiguration].
==> windows-2025-vs2026.azure-arm.image: At C:\Windows\Temp\script-69d3d4be-a53b-cd3f-3aa2-efa7e92eb6d8.ps1:58 char:1
==> windows-2025-vs2026.azure-arm.image: + Invoke-PesterTests -TestFile "Docker" -TestName "Docker"
==> windows-2025-vs2026.azure-arm.image: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> windows-2025-vs2026.azure-arm.image: + CategoryInfo : InvalidOperation: (PesterConfiguration:TypeName) [Invoke-PesterTests], RuntimeException
==> windows-2025-vs2026.azure-arm.image: + FullyQualifiedErrorId : TypeNotFound,Invoke-PesterTests
==> windows-2025-vs2026.azure-arm.image:
==> windows-2025-vs2026.azure-arm.image: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]
==> windows-2025-vs2026.azure-arm.image: Step "StepProvision" failed
Previous build was successful, using the same configuration
Repro steps
Rerun the steps
Description
==> windows-2025-vs2026.azure-arm.image: Invoke-PesterTests : Unable to find type [PesterConfiguration].
==> windows-2025-vs2026.azure-arm.image: At C:\Windows\Temp\script-69d3d4be-a53b-cd3f-3aa2-efa7e92eb6d8.ps1:58 char:1
==> windows-2025-vs2026.azure-arm.image: + Invoke-PesterTests -TestFile "Docker" -TestName "Docker"
==> windows-2025-vs2026.azure-arm.image: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> windows-2025-vs2026.azure-arm.image: + CategoryInfo : InvalidOperation: (PesterConfiguration:TypeName) [Invoke-PesterTests], RuntimeException
==> windows-2025-vs2026.azure-arm.image: + FullyQualifiedErrorId : TypeNotFound,Invoke-PesterTests
==> windows-2025-vs2026.azure-arm.image:
==> windows-2025-vs2026.azure-arm.image: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]
==> windows-2025-vs2026.azure-arm.image: Step "StepProvision" failed
Platforms affected
Runner images affected
Image version and build link
Generating new image
Is it regression?
na
Expected behavior
Scheduled task should be created and executed successfully.
Actual behavior
==> windows-2025-vs2026.azure-arm.image: Invoke-PesterTests : Unable to find type [PesterConfiguration].
==> windows-2025-vs2026.azure-arm.image: At C:\Windows\Temp\script-69d3d4be-a53b-cd3f-3aa2-efa7e92eb6d8.ps1:58 char:1
==> windows-2025-vs2026.azure-arm.image: + Invoke-PesterTests -TestFile "Docker" -TestName "Docker"
==> windows-2025-vs2026.azure-arm.image: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> windows-2025-vs2026.azure-arm.image: + CategoryInfo : InvalidOperation: (PesterConfiguration:TypeName) [Invoke-PesterTests], RuntimeException
==> windows-2025-vs2026.azure-arm.image: + FullyQualifiedErrorId : TypeNotFound,Invoke-PesterTests
==> windows-2025-vs2026.azure-arm.image:
==> windows-2025-vs2026.azure-arm.image: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]
==> windows-2025-vs2026.azure-arm.image: Step "StepProvision" failed
Previous build was successful, using the same configuration
Repro steps
Rerun the steps