Skip to content

Increase timeout for pack tests

Azure Pipelines / NuGet.Client CI (Functional Tests on Windows (.NET Core 3.1) Functional Tests on Windows (.NET Core 3.1)) failed Jun 30, 2024 in 5m 38s

Functional Tests on Windows (.NET Core 3.1) Functional Tests on Windows (.NET Core 3.1) failed

4 errors / 0 warnings

Annotations

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI (Functional Tests on Windows (.NET Core 3.1) Functional Tests on Windows (.NET Core 3.1))

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI (Functional Tests on Windows (.NET Core 3.1) Functional Tests on Windows (.NET Core 3.1))

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI (Functional Tests on Windows (.NET Core 3.1) Functional Tests on Windows (.NET Core 3.1))

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI (Functional Tests on Windows (.NET Core 3.1) Functional Tests on Windows (.NET Core 3.1))

Build log #L128 

Process 'msbuild.exe' exited with code '1'.
View more details on Azure Pipelines