Known issue: NuGet "FatalProtocolException : Unable to load the service index" #90951
Comments
steveharter
added
the
Known Build Error
|
#82431 (comment) mentions the underlying test issue. As nothing in the shared infrastructure should be making requests to nuget.org, I'm moving this issue to the runtime repo where the failing test lives. |
dotnet-issue-labeler
bot
added
the
needs-area-label
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBuildAppears to be a known NuGet connectivity issue; adding template to catch these: Build leg reportedGC_API.WorkItemExecution Pull RequestKnown issue core informationFill out the known issue JSON section by following the step by step documentation on how to create a known issue {
"ErrorMessage" : "NuGet.Protocol.Core.Types.FatalProtocolException : Unable to load the service index for source https://api.nuget.org/v3/index.json.",
"BuildRetry": false
}@dotnet/dnceng Release Note Category
Release Note DescriptionAdditional information about the issue reportedNo response Known issue validationBuild: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=382187 Report
Summary
|
jkotas
removed
the
needs-area-label
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsBuildAppears to be a known NuGet connectivity issue; adding template to catch these: Build leg reportedGC_API.WorkItemExecution Pull RequestKnown issue core informationFill out the known issue JSON section by following the step by step documentation on how to create a known issue {
"ErrorMessage" : "NuGet.Protocol.Core.Types.FatalProtocolException : Unable to load the service index for source https://api.nuget.org/v3/index.json.",
"BuildRetry": false
}@dotnet/dnceng Release Note Category
Release Note DescriptionAdditional information about the issue reportedNo response Known issue validationBuild: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=382187 ReportSummary
|
Yikes! Do we really want our analyzer tests accessing NuGet.org to try to fetch reference assemblies? That doesn't seem right. @sharwell do you think these tests are missing something to tell the test framework where to find reference assemblies. Those must be available as part of the helix payload... |
|
We have a mechanism in this repo to use the live Reference Pack. We should use it. Alternatively, since this analyzer is just for CoreLib, we should configure the tests to only pull in CoreLib as a reference. |
…Tests This avoids an issue where the analyzer test tries to restore reference assemblies from nuget.org during the test. We already have helpers in place to use the live reference pack instead. Fixes dotnet#90951 Fixes dotnet#93103
ghost
added
the
in-pr
ghost
removed
in-pr
ghost
locked as resolved and limited conversation to collaborators
Build
https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=382187
Appears to be a known NuGet connectivity issue; adding template to catch these:
#81586
#33294
Build leg reported
GC_API.WorkItemExecution
Pull Request
#90796
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
{ "ErrorMessage" : "NuGet.Protocol.Core.Types.FatalProtocolException : Unable to load the service index for source https://api.nuget.org/v3/index.json.", "BuildRetry": false }@dotnet/dnceng
Release Note Category
Release Note Description
Additional information about the issue reported
No response
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=382187
Error message validated:
NuGet.Protocol.Core.Types.FatalProtocolException : Unable to load the service index for source https://api.nuget.org/v3/index.json.Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/22/2023 8:25:55 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: