-
Notifications
You must be signed in to change notification settings - Fork 474
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
Repeated ECONNRESET errors in setup-dotnet action #333
Comments
Hi, @AaronFriel 👋 I see the problem in your repo, but unfortunately, I can't reproduce it. It was probably a temporary problem on the side of the MS .NET SDKs dist, our action relies on it and it explains why the installation of SDK for all OS was blocked. |
@IvanZosimov Would it make sense to engineer around this or mirror their distribution info? Would it be possible to add some logging to this action so that when net requests fail, the URL requested is logged? |
@AaronFriel , Sure! We are working on this issue now. |
I'm getting this error now: https://github.com/recyclarr/recyclarr/actions/runs/3252206657/jobs/5338195677#step:3:36 |
I'm also seeing this. Not sure if it helps, but this is the error:
This is my workflow yml:
|
Hi, @rcdailey and @joelwkall, thanks for your comments. We are still in the process of investigation. You can upgrade the version of the |
I'm also quite often facing this issue using this GitHub Action. 😢 |
Hello everyone! |
For now I'm going to close the issue. If you have any concerns feel free to ping us. |
Description:
Roughly 70% of merge jobs in the pulumi/pulumi repo are failing due to a high failure rate on actions/setup-dotnet@v2.
No additional logs are present. We are running with these arguments:
Task version:
actions/setup-dotnet@v2
Platform:
Failures have occurred on all three platforms.
Runner type:
Repro steps:
Unsure of steps to reproduce - we run a large number of jobs to validate all merges (on the order of ~100), and in more than half of the workflows in the past 24 hours the workflow failed due to
Expected behavior:
Action should succeed.
Actual behavior:
Action fails catastrophically on a network issue.
Example failures:
The text was updated successfully, but these errors were encountered: