Gather test diag logging to track down nuget issue #44455
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We're seeing NU3003 for packages that when downloaded manually, don't show an issue. Per NuGet team, this means an exception is thrown and collecting verbosity information should help. I believe I've mostly seen this on windows so let's enable for windows and just keep rerunning until we hit it.
dotnet-issue-labeler
bot
added
Area-Infrastructure
untriaged
…t run and makes it hard to track down.
|
/azp run dotnet-sdk-public-ci,sdk-source-build,sdk-unified-build |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run dotnet-sdk-public-ci,sdk-source-build,sdk-unified-build |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run dotnet-sdk-public-ci,sdk-source-build,sdk-unified-build |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
@dsplaisted per offline chat, if we hit this it can happen multiple times in a single run so I think it's safe to rerun the build as we'll likely see the error again. Here's an example where that happened recently (one of the helix legs I clicked on had 7 tests fail with the same NU3003 warning). If you're ok checking this in and waiting until it fails again to investigate, please take a look. |
dsplaisted
approved these changes
Oct 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We're seeing NU3003 for packages that when downloaded manually, don't show an issue. Per NuGet team, this means an exception is thrown and collecting verbosity information should help.
I believe I've mostly seen this on windows so let's enable for windows and just keep rerunning until we hit it.