-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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.
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
dotnet workload
is broken on windows-latest runner image 20250113.1.0
#11402
Comments
Possibly also affects Azure DevOps if dotnet/sdk#45931 is anything to go by, but I have no means to verify. |
All our dotnet builds are failing now with A simple way to reproduce it is to run jobs:
- job: MyJob
pool:
vmImage: 'windows-2022'
steps:
- checkout: self
- script: 'dotnet --info' Here is an extract of the logs:
|
Hi @bdach - Thank you for bringing this issue to our attention. We will look into this issue closely and will update you after investigating. Additionally, latest windows image version is going to roll out. Will update you on this. |
Any news here? We are stuck aswell.. |
Indeed the 2022 vmimage is broken all of a sudden. But the windows-2019 vmimage works. |
I am seeing the same thing on a few private repositories as well. The |
Description
First noticed via android builds starting to fail intermittently out of nowhere after no changes on our behalf.
Upon throwing several workarounds at the problem and failing every one (which was made even more difficult by the fact that the build is half-rolled-out, therefore the failure only occurs in ~15% of builds queued, and this is not the first time this sort of thing has happened, by the way), I can't come to a conclusion other than just say that
dotnet workload
has become terminally broken somehow, because even a baredotnet workload search
fails with the exact same error.Platforms affected
Runner images affected
Image version and build link
Is it regression?
Yes, last working version was 20250105.1.0
Expected behavior
(https://github.com/bdach/osu/actions/runs/12805144936/job/35700930330#step:5:1)
Actual behavior
(https://github.com/bdach/osu/actions/runs/12805144936/job/35701092126#step:5:1)
Repro steps
I believe this job definition should be sufficient to reproduce and minimal enough to not require testing on the original project:
As long as you actually get lucky enough to run on the correct runner image version, that is.
The text was updated successfully, but these errors were encountered: