-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Flaky network / nuget downloads #10654
Comments
Hi @thomhurst , Thank you for bringing this issue to us. We are looking into this issue and will update you on this issue after investigating. |
It being particularly problematic for the last couple of weeks might be related to NuGet/Home#13729. |
@thomhurst Could you please confirm the platform on which you are facing an issue? |
All OSs. So maybe @JonathanLydall is right with it being an SDK issue? Windows: https://github.com/thomhurst/TUnit/actions/runs/10884782402/job/30200836426 Mac: https://github.com/thomhurst/ModularPipelines/actions/runs/10948383717/job/30399283041 Linux: https://github.com/thomhurst/TUnit/actions/runs/10880746543/job/30188233765 |
We've been seeing similar issues on macOS the last few days that Swift Package Manager tests that use binary dependencies are almost always failing with |
Using the |
Sounds like they're workarounds that can help, but ultimately there's an issue that needs fixing |
Hi @thomhurst Could you please try with the below workaround. |
Hi @thomhurst Hope your issue resolves by using the below workaround.
Thanks, Closing this issue for now. |
Description
I've seen this for a couple of months now. Fairly often NuGet will error my pipelines with failures to download a package. Happens way too frequently nowadays so I assume something is wrong somewhere?
Platforms affected
Runner images affected
Image version and build link
https://github.com/thomhurst/ModularPipelines/actions/runs/10948383717/job/30399283041
Is it regression?
Yes?
Expected behavior
Download succeeds
Actual behavior
Download fails
Repro steps
dotnet restore
The text was updated successfully, but these errors were encountered: