-
Notifications
You must be signed in to change notification settings - Fork 1.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
SDK build sporadically failing due to multiple pipelines trying to concurrently upload 'BlobArtifacts/dotnet-toolset-internal-6.0.100-ci.zip' #19679
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
This is happening regularly, eg., in the maestro ingestion today for runtime both are the full framework ones -- probably because they take about the same time. Both are trying to upload the same blob 'BlobArtifacts/dotnet-toolset-langpack-6.0.100-ci.zip' @marcpopMSFT this is probably important to look into because we don't know what is getting uploaded, whether it's corrupted etc. It's also causing retries which consume resources. |
I'll take a look today. We probably only need one or need to add the configuration property as a discriminator. |
So this is a zip that contains the full SDK. Looks like it's being used as a transport for dotnet/installer that we then unzip and harvest into the .NET SDK installer. Not sure why we have the langpack, because the normal zip contains the resource assemblies already. @dsplaisted any concerns if we only publish this for the release build? |
I searched dotnet for dotnet-toolset-internal references. It only shows the SDK, but it's used in the installer repo, so now I'm not sure if I should trust the search. I'm trying to determine whether anyone else besides dotnet/installer depends on this artifact |
Chatted with a few folks. We can just turn off publishing on the debug leg for CI. |
Jacques made a fix that we think is sufficient. Closing and can reactivate if we see more instances that we're sure include the fix (not sure about Larry's pipeline or not) |
I'm seeing this in https://github.com/dotnet/sdk/pull/21453/checks?check_run_id=3726720363
|
This issue is being discussed in arcade |
Latest fix for this potentially here: https://github.com/dotnet/sdk/pull/27899/files I think briefly templating made this more common in the past by accidentally publishing and that gave us enough impetus to figure out what was likely going on (-publish was automatically set by one of the scripts we were using) |
This may possibly just corrupt the blob instead. @joeloff is investigating. We probably should prioritize fixing...
Same thing happened here:
#19582 (comment)
See also dotnet/core-eng#14015
@dotnet/domestic-cat
The text was updated successfully, but these errors were encountered: