-
Notifications
You must be signed in to change notification settings - Fork 256
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
ArgumentNullException from NuGet calls in Microsoft.CodeAnalysis.Testing.ReferenceAssemblies.ResolveAsync #974
Comments
Another hit in https://dev.azure.com/dnceng/public/_build/results?buildId=1674834&view=ms.vss-test-web.build-test-results-tab&runId=45943994&resultId=151060&paneView=debug, so this isn't a one-off. cc: @sharwell |
We're hitting this pretty often in dotnet/runtime, so it's definitely not a one-off failure. |
This is now happening 10x a day in dotnet/runtime @jaredpar @sharwell could someone please take a look? TestResults
| join kind=inner WorkItems on WorkItemId
| join kind=inner Jobs on JobId
| where Finished >= now(-2d)
| where Result == "Fail"
| where Message startswith "System.ArgumentNullException : Value cannot be null. (Parameter 'package"
| project Type, Method,
Pipeline = tostring(parse_json(Properties).DefinitionName),//WorkItemFriendlyName,
Pipeline_Configuration = tostring(parse_json(Properties).configuration),
OS = QueueName,
Arch = tostring(parse_json(Properties).architecture),
Finished,
Build
|
pasting stack
|
I am not familiar with this code or NuGet code. But I see that GetDownloadResourceResultAsync can succeed and return a DownloadResourceResult with a null packageStream. I am not sure what that means (unless it's just another kind of error). Should the code at the point of the exception above treat |
We recently hit an
ArgumentNullException
that stemmed from us using theReferenceAssemblies
API in dotnet/runtime. This occurred in dotnet/runtime#66952 on macOS x64 (Helix Log here).This looks like it may have been a one-off failure, but I wanted to report it in case it's reproducible as even one-off-style failures can cause significant issues keeping dotnet/runtime green.
The text was updated successfully, but these errors were encountered: