-
Notifications
You must be signed in to change notification settings - Fork 19
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
File upload failed even after retry #1916
Labels
Comments
This is often an from multiple lanes attempting to upload the same artifact |
@lewing is right - there's usually not a whole lot dnceng can do to help. |
akoeplinger
added a commit
to dotnet/runtime
that referenced
this issue
Nov 9, 2024
) We're occasionally seeing errors on the official build during artifacts upload (dotnet/dnceng#1916) This is because multiple jobs are trying to push the Microsoft.NETCore.App.Ref nuget package to the same AzDO build artifacts container, causing conflicts. Since we'll be using the VMR in the near future and it is using a different asset selection the quick fix is to just delete the package on the jobs where it's not supposed to be uploaded rather than trying to introduce a complicated condition in msbuild.
mikelle-rogers
pushed a commit
to mikelle-rogers/runtime
that referenced
this issue
Dec 10, 2024
…et#109650) We're occasionally seeing errors on the official build during artifacts upload (dotnet/dnceng#1916) This is because multiple jobs are trying to push the Microsoft.NETCore.App.Ref nuget package to the same AzDO build artifacts container, causing conflicts. Since we'll be using the VMR in the near future and it is using a different asset selection the quick fix is to just delete the package on the jobs where it's not supposed to be uploaded rather than trying to introduce a complicated condition in msbuild.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Build
https://dev.azure.com/dnceng/internal/_build/results?buildId=2365835
Error:
Build leg reported
No response
Pull Request
No response
Known issue core information
Fill out the known issue JSON section by following the step by step documentation on how to create a known issue
@dotnet/dnceng
Release Note Category
Release Note Description
Additional information about the issue reported
No response
Report
Summary
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng/internal/_build/results?buildId=2365835
Error message validated:
[##[error]File upload failed even after retry
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/7/2024 2:03:27 AM UTC
The text was updated successfully, but these errors were encountered: