Skip to content

fix build

dcd93dd
Select commit
Loading
Failed to load commit list.
Draft

Migrate to xunit v3 #7273

fix build
dcd93dd
Select commit
Loading
Failed to load commit list.
Azure Pipelines / NuGet.Client CI failed Apr 18, 2026 in 45m 40s

Build #20260417.16 had test failures

Details

Tests

  • Failed: 10 (0.02%)
  • Passed: 61,381 (98.26%)
  • Other: 1,074 (1.72%)
  • Total: 62,465

Annotations

Check failure on line 15 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI

Build log #L15

Cmd.exe exited with code '128'.

Check failure on line 57 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI

Build log #L57

Error: The process 'D:\a\_work\1\s\cli\dotnet.exe' failed with exit code 1

Check failure on line 62 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI

Build log #L62

Dotnet command failed with non-zero exit code on the following projects : [ '' ]

Check failure on line 15 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI

Build log #L15

Cmd.exe exited with code '128'.

Check failure on line 1 in NuGet.CommandLine.FuncTest.CommandRunnerTest.Run_TimesOut

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI

NuGet.CommandLine.FuncTest.CommandRunnerTest.Run_TimesOut

Expected stopwatch.Elapsed.TotalSeconds to be less than or equal to 2.0, but found 9.178021 (difference of 7.1780209999999993).
Raw output
   at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message)
   at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason)
   at FluentAssertions.Numeric.NumericAssertionsBase`3.BeLessThanOrEqualTo(T expected, String because, Object[] becauseArgs)
   at NuGet.CommandLine.FuncTest.CommandRunnerTest.Run_TimesOut() in D:\a\_work\1\s\test\NuGet.Clients.FuncTests\NuGet.CommandLine.FuncTest\CommandRunnerTest.cs:line 200

Check failure on line 1 in Dotnet.Integration.Test.DotnetSignTests.DotnetSign_SignPackageWithTrustedCertificateWithRelativePath_SucceedsAsync

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI

Dotnet.Integration.Test.DotnetSignTests.DotnetSign_SignPackageWithTrustedCertificateWithRelativePath_SucceedsAsync

Expected result.ExitCode to be 0 because D:\a\_work\1\s\.test\work\a3ea2c8b\05660096\dotnet.exe nuget sign .\PackageA.1.0.0.nupkg --certificate-fingerprint 30A9741FF2DECD49CCF7C681C69FC8E252229FF302565C40787610FC99C1B0C3 --certificate-store-name My --certificate-store-location CurrentUser should have succeeded but returned exit code 1 after 0.4s with the following output:
warn : NU3002: The '--timestamper' option was not provided. The signed package will not be timestamped. To learn more about this option, please visit https://docs.microsoft.com/dotnet/core/tools
error: NU3001: No certificates were found that meet all the given criteria. For a list of accepted ways to provide a certificate, visit https://docs.nuget.org/docs/reference/command-line-reference
error: NuGet.Commands.SignCommandException: No certificates were found that meet all the given criteria. For a list of accepted ways to provide a certificate, visit https://docs.nuget.org/docs/reference/command-line-reference
error:    at NuGet.Commands.SignCommandRunner.GetCertificateAsync(SignArgs signArgs) in D:\a\_work\1\s\src\NuGet.Core\NuGet.Commands\SignCommand\SignCommandRunner.cs:line 234
error:    at NuGet.Commands.SignCommandRunner.ExecuteCommandAsync(SignArgs signArgs) in D:\a\_work\1\s\src\NuGet.Core\NuGet.Commands\SignCommand\SignCommandRunner.cs:line 40

, but found 1 (difference of 1).
Raw output
   at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message)
   at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
   at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason)
   at FluentAssertions.Numeric.NumericAssertionsBase`3.Be(T expected, String because, Object[] becauseArgs)
   at Dotnet.Integration.Test.DotnetIntegrationTestFixture.RunDotnet(String workingDirectory, String args, Boolean expectSuccess, IReadOnlyDictionary`2 environmentVariables, Action`1 logLine, Action`1 inputAction) in D:\a\_work\1\s\test\NuGet.Core.FuncTests\Dotnet.Integration.Test\DotnetIntegrationTestFixture.cs:line 232
   at Dotnet.Integration.Test.DotnetIntegrationTestFixture.RunDotnetExpectSuccess(String workingDirectory, String args, IReadOnlyDictionary`2 environmentVariables, Action`1 logLine, Action`1 inputAction) in D:\a\_work\1\s\test\NuGet.Core.FuncTests\Dotnet.Integration.Test\DotnetIntegrationTestFixture.cs:line 163
   at Dotnet.Integration.Test.DotnetSignTests.DotnetSign_SignPackageWithTrustedCertificateWithRelativePath_SucceedsAsync() in D:\a\_work\1\s\test\NuGet.Core.FuncTests\Dotnet.Integration.Test\DotnetSignTests.cs:line 80
--- End of stack trace from previous location ---

Check failure on line 1 in Dotnet.Integration.Test.DotnetSignTests.DotnetSign_SignPackageWithTimestamping_SucceedsAsync

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI

Dotnet.Integration.Test.DotnetSignTests.DotnetSign_SignPackageWithTimestamping_SucceedsAsync

Expected result.ExitCode to be 0 because D:\a\_work\1\s\.test\work\a3ea2c8b\05660096\dotnet.exe nuget sign D:\a\_work\1\s\.test\work\4288b013\c94ec927\source\PackageA.1.0.0.nupkg --certificate-fingerprint 30A9741FF2DECD49CCF7C681C69FC8E252229FF302565C40787610FC99C1B0C3 --certificate-store-name My --certificate-store-location CurrentUser --timestamper http://127.0.0.1:54637/EB7EEFC6BF3F2DE6D9E55C240FFA1E1F5D97A17C15FAB0B37D2074E710243A84/ should have succeeded but returned exit code 1 after 0.4s with the following output:
error: NU3001: No certificates were found that meet all the given criteria. For a list of accepted ways to provide a certificate, visit https://docs.nuget.org/docs/reference/command-line-reference
error: NuGet.Commands.SignCommandException: No certificates were found that meet all the given criteria. For a list of accepted ways to provide a certificate, visit https://docs.nuget.org/docs/reference/command-line-reference
error:    at NuGet.Commands.SignCommandRunner.GetCertificateAsync(SignArgs signArgs) in D:\a\_work\1\s\src\NuGet.Core\NuGet.Commands\SignCommand\SignCommandRunner.cs:line 234
error:    at NuGet.Commands.SignCommandRunner.ExecuteCommandAsync(SignArgs signArgs) in D:\a\_work\1\s\src\NuGet.Core\NuGet.Commands\SignCommand\SignCommandRunner.cs:line 40

, but found 1 (difference of 1).
Raw output
   at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message)
   at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
   at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason)
   at FluentAssertions.Numeric.NumericAssertionsBase`3.Be(T expected, String because, Object[] becauseArgs)
   at Dotnet.Integration.Test.DotnetIntegrationTestFixture.RunDotnet(String workingDirectory, String args, Boolean expectSuccess, IReadOnlyDictionary`2 environmentVariables, Action`1 logLine, Action`1 inputAction) in D:\a\_work\1\s\test\NuGet.Core.FuncTests\Dotnet.Integration.Test\DotnetIntegrationTestFixture.cs:line 232
   at Dotnet.Integration.Test.DotnetIntegrationTestFixture.RunDotnetExpectSuccess(String workingDirectory, String args, IReadOnlyDictionary`2 environmentVariables, Action`1 logLine, Action`1 inputAction) in D:\a\_work\1\s\test\NuGet.Core.FuncTests\Dotnet.Integration.Test\DotnetIntegrationTestFixture.cs:line 163
   at Dotnet.Integration.Test.DotnetSignTests.DotnetSign_SignPackageWithTimestamping_SucceedsAsync() in D:\a\_work\1\s\test\NuGet.Core.FuncTests\Dotnet.Integration.Test\DotnetSignTests.cs:line 183
--- End of stack trace from previous location ---

Check failure on line 1 in Dotnet.Integration.Test.DotnetSignTests.DotnetSign_SignPackageWithPfxFileOfRelativePath_SuccessAsync

See this annotation in the file changed.

@azure-pipelines azure-pipelines / NuGet.Client CI

Dotnet.Integration.Test.DotnetSignTests.DotnetSign_SignPackageWithPfxFileOfRelativePath_SuccessAsync

Expected result.ExitCode to be 0 because D:\a\_work\1\s\.test\work\a3ea2c8b\05660096\dotnet.exe nuget sign D:\a\_work\1\s\.test\work\6ef45b6e\33e85114\source\PackageA.1.0.0.nupkg --certificate-path .\90356c5f-996c-4a1c-8f7f-3061e51b1282.pfx --certificate-password c0a5c5fc-3305-4827-974d-2202e237b04a should have succeeded but returned exit code 1 after 0.4s with the following output:
warn : NU3002: The '--timestamper' option was not provided. The signed package will not be timestamped. To learn more about this option, please visit https://docs.microsoft.com/dotnet/core/tools
error: NU3018: NotTimeValid: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
warn : NU3018: RevocationStatusUnknown: The revocation function was unable to check revocation for the certificate.
warn : NU3018: OfflineRevocation: The revocation function was unable to check revocation because the revocation server was offline.
error: NU3018: Certificate chain validation failed.
error: NuGet.Packaging.Signing.SignatureException: Certificate chain validation failed.
error:    at NuGet.Packaging.Signing.CertificateChainUtility.GetCertificateChain(X509Certificate2 certificate, X509Certificate2Collection extraStore, ILogger logger, CertificateType certificateType, Boolean allowUntrustedRoot) in D:\a\_work\1\s\src\NuGet.Core\NuGet.Packaging\Signing\Utility\CertificateChainUtility.cs:line 133
error:    at NuGet.Packaging.Signing.SignPackageRequest.BuildSigningCertificateChainOnce(ILogger logger) in D:\a\_work\1\s\src\NuGet.Core\NuGet.Packaging\Signing\Authoring\SignPackageRequest.cs:line 115
error:    at NuGet.Packaging.Signing.SigningUtility.Verify(SignPackageRequest request, ILogger logger) in D:\a\_work\1\s\src\NuGet.Core\NuGet.Packaging\Signing\Utility\SigningUtility.cs:line 53
error:    at NuGet.Commands.SignCommandRunner.ExecuteCommandAsync(IEnumerable`1 packagesToSign, SignPackageRequest signPackageRequest, String timestamper, ILogger logger, String outputDirectory, Boolean overwrite, CancellationToken token) in D:\a\_work\1\s\src\NuGet.Core\NuGet.Commands\SignCommand\SignCommandRunner.cs:line 100

, but found 1 (difference of 1).
Raw output
   at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message)
   at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
   at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason)
   at FluentAssertions.Numeric.NumericAssertionsBase`3.Be(T expected, String because, Object[] becauseArgs)
   at Dotnet.Integration.Test.DotnetIntegrationTestFixture.RunDotnet(String workingDirectory, String args, Boolean expectSuccess, IReadOnlyDictionary`2 environmentVariables, Action`1 logLine, Action`1 inputAction) in D:\a\_work\1\s\test\NuGet.Core.FuncTests\Dotnet.Integration.Test\DotnetIntegrationTestFixture.cs:line 232
   at Dotnet.Integration.Test.DotnetIntegrationTestFixture.RunDotnetExpectSuccess(String workingDirectory, String args, IReadOnlyDictionary`2 environmentVariables, Action`1 logLine, Action`1 inputAction) in D:\a\_work\1\s\test\NuGet.Core.FuncTests\Dotnet.Integration.Test\DotnetIntegrationTestFixture.cs:line 163
   at Dotnet.Integration.Test.DotnetSignTests.DotnetSign_SignPackageWithPfxFileOfRelativePath_SuccessAsync() in D:\a\_work\1\s\test\NuGet.Core.FuncTests\Dotnet.Integration.Test\DotnetSignTests.cs:line 415
--- End of stack trace from previous location ---