You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Build failure in Microsoft.Extensions.HostFactoryResolver.Tests: xunit.assert 2.4.2 - author primary signature's signing certificate is not trusted by the trust provider #75040
##[error]src\libraries\Microsoft.Extensions.HostFactoryResolver\tests\Microsoft.Extensions.HostFactoryResolver.Tests.csproj(0,0):
error NU3018: (NETCORE_ENGINEERING_TELEMETRY=Restore) Package 'xunit.assert 2.4.2' from source 'https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json':
The author primary signature's signing certificate is not trusted by the trust provider.
@carlossanlop do you see this happened again or just one failure instance? looks not a real failure and something was happening during the run.
CC @MattGal dotnet/dceng any idea what could be the problem?
This is the second time, out of many thousands of instances, that I've seen this. I think it's a very brief transient issue in certificate validation happening but without a repro it's quite difficult to investigate.
src\libraries\Microsoft.Extensions.HostFactoryResolver\tests\Microsoft.Extensions.HostFactoryResolver.Tests.csproj(0,0): error NU3018: (NETCORE_ENGINEERING_TELEMETRY=Restore) Package 'xunit.extensibility.execution 2.4.2' from source 'https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json': The author primary signature's signing certificate is not trusted by the trust provider.
Activity
tarekgh commentedon Sep 6, 2022
@carlossanlop do you see this happened again or just one failure instance? looks not a real failure and something was happening during the run.
CC @MattGal @dotnet/dnceng any idea what could be the problem?
MattGal commentedon Sep 6, 2022
This is the second time, out of many thousands of instances, that I've seen this. I think it's a very brief transient issue in certificate validation happening but without a repro it's quite difficult to investigate.
tarekgh commentedon Sep 6, 2022
Thanks @MattGal. I am closing it as it looks like no action for now. We can look more if we get it again.
carlossanlop commentedon Sep 9, 2022
FYI I just saw it again in a release/7.0 backport PR: #75308