Increase timeout for pack tests · NuGet/NuGet.Client@e6aabcc · GitHub

Azure Pipelines / NuGet.Client CI (Functional Tests on Windows (.NET Framework 4.7.2) Functional Tests on Windows (.NET Framework 4.7.2)) failed Jun 30, 2024 in 5m 48s

Functional Tests on Windows (.NET Framework 4.7.2) Functional Tests on Windows (.NET Framework 4.7.2) failed

4 errors / 0 warnings

Annotations

Check failure on line 85 in test\TestUtilities\Test.Utility\CommandRunner.cs

azure-pipelines / NuGet.Client CI (Functional Tests on Windows (.NET Framework 4.7.2) Functional Tests on Windows (.NET Framework 4.7.2))

test\TestUtilities\Test.Utility\CommandRunner.cs#L85

test\TestUtilities\Test.Utility\CommandRunner.cs(85,71): Error CS0103: The name 'attempt' does not exist in the current context

Check failure on line 85 in test\TestUtilities\Test.Utility\CommandRunner.cs

azure-pipelines / NuGet.Client CI (Functional Tests on Windows (.NET Framework 4.7.2) Functional Tests on Windows (.NET Framework 4.7.2))

test\TestUtilities\Test.Utility\CommandRunner.cs#L85

test\TestUtilities\Test.Utility\CommandRunner.cs(85,71): Error CS0103: The name 'attempt' does not exist in the current context

Check failure on line 85 in test\TestUtilities\Test.Utility\CommandRunner.cs

azure-pipelines / NuGet.Client CI (Functional Tests on Windows (.NET Framework 4.7.2) Functional Tests on Windows (.NET Framework 4.7.2))

test\TestUtilities\Test.Utility\CommandRunner.cs#L85

test\TestUtilities\Test.Utility\CommandRunner.cs(85,71): Error CS0103: The name 'attempt' does not exist in the current context

Check failure on line 128 in Build log

azure-pipelines / NuGet.Client CI (Functional Tests on Windows (.NET Framework 4.7.2) Functional Tests on Windows (.NET Framework 4.7.2))

Build log #L128

Process 'msbuild.exe' exited with code '1'.

View more details on Azure Pipelines