Test: NuGet.CommandLine.Test.NuGetPushCommandTest.PushCommand_PushToServer_WhenPluginTimesOut_ThrowsAndDoesNotFallBackToConsoleProvider is flaky
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.6k
- Forks
- 276
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 1
Description
Test NuGet.CommandLine.Test.NuGetPushCommandTest.PushCommand_PushToServer_WhenPluginTimesOut_ThrowsAndDoesNotFallBackToConsoleProvider is flaky.
System.TimeoutException : NuGet.exe timed out: push E:\\A\\_work\\279\\s\\.test\\work\\e1971ebd\\2ac4581d\\testPackage1.1.1.0.nupkg -Source http://localhost:50231/c5f508e4-7619-48ef-a899-cdccdc7d084e/nuget
at NuGet.Test.Utility.CommandRunner.Run(String process, String workingDirectory, String arguments, Boolean waitForExit, Int32 timeOutInMilliseconds, Action`1 inputAction, Boolean shareProcessObject, IDictionary`2 environmentVariables) in E:\A\_work\279\s\test\TestUtilities\Test.Utility\CommandRunner.cs:line 88
at NuGet.CommandLine.Test.NuGetPushCommandTest.PushCommand_PushToServer_WhenPluginTimesOut_ThrowsAndDoesNotFallBackToConsoleProvider() in E:\A\_work\279\s\test\NuGet.Clients.Tests\NuGet.CommandLine.Test\NuGetPushCommandTest.cs:line 1265
From test history it appears that the test is consistently near its 10 second timeout.

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with test/NuGet.Clients.Tests/NuGet.CommandLine.Test/NuGetPushCommandTest.cs at line 1265 and review test/TestUtilities/Test.Utility/CommandRunner.cs at line 88. Run PushCommand_PushToServer_WhenPluginTimesOut_ThrowsAndDoesNotFallBackToConsoleProvider repeatedly, then determine why it approaches the 10-second timeout. Done means the test reliably verifies the timeout behavior without intermittent process timeouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100