You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is just to get a bearing if others have the same experience that I have.
We create 3 ubuntu buildserver 2004,2204 and 2404 and they all go well.
But the windows2019 and windows2022 takes up to 5+ hours and both often fails.
Windows2019 fails with this after 3 hours:
==> windows.azure-arm.windowsbuildserver: Warning: Failed to find package 'extras;m2repository;com;android;support;constraint;constraint-layout-solver;1.0.2'
==> windows.azure-arm.windowsbuildserver: Warning: Failed to find package 'extras;m2repository;com;android;support;constraint;constraint-layout-solver;1.0.1'
==> windows.azure-arm.windowsbuildserver: Warning: Failed to find package 'extras;m2repository;com;android;support;constraint;constraint-layout;1.0.2'
==> windows.azure-arm.windowsbuildserver: Warning: Failed to find package 'extras;m2repository;com;android;support;constraint;constraint-layout;1.0.1'
windows.azure-arm.windowsbuildserver: [=== ] 10% Computing updates...
==> windows.azure-arm.windowsbuildserver: Failed to install package extras;m2repository;com;android;support;constraint;constraint-layout-solver;1.0.2 with exit
And Windows2022 fails with this after 5+ hours:
==> windows.azure-arm.windowsbuildserver: Provisioning with powershell script: /home/vsts/azagent/a1/_work/2/windows2022/images/windows/templates/../scripts/build/Install-NativeImages.ps1
windows.azure-arm.windowsbuildserver: NGen: install Microsoft.PowerShell.Utility.Activities...
windows.azure-arm.windowsbuildserver: NGen: update x64 native images...
==> windows.azure-arm.windowsbuildserver: Update of x64 native images failed with exit code -1
==> windows.azure-arm.windowsbuildserver: At C:\Windows\Temp\script-66b419b0-e12c-354b-8efc-1e142a80b750.ps1:15 char:5
==> windows.azure-arm.windowsbuildserver: + throw "Update of x64 native images failed with exit code $LASTEXI ...
==> windows.azure-arm.windowsbuildserver: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> windows.azure-arm.windowsbuildserver: + CategoryInfo : OperationStopped: (Update of x64 n...th exit code -1:String) [], RuntimeException
==> windows.azure-arm.windowsbuildserver: + FullyQualifiedErrorId : Update of x64 native images failed with exit code -1
==> windows.azure-arm.windowsbuildserver:
We are using azure pipelines to create the images, using Azure as backbone for the vm's.
At the moment we only have ubuntu buildservers and no windows as they simply can't get created.
This has been a problem since we started using runner images back in in 2021, where windows were very unstable.
Does anybody else have this issue or are we alone?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This is just to get a bearing if others have the same experience that I have.
We create 3 ubuntu buildserver 2004,2204 and 2404 and they all go well.
But the windows2019 and windows2022 takes up to 5+ hours and both often fails.
Windows2019 fails with this after 3 hours:
And Windows2022 fails with this after 5+ hours:
We are using azure pipelines to create the images, using Azure as backbone for the vm's.
At the moment we only have ubuntu buildservers and no windows as they simply can't get created.
This has been a problem since we started using runner images back in in 2021, where windows were very unstable.
Does anybody else have this issue or are we alone?
Beta Was this translation helpful? Give feedback.
All reactions