Networking certificate test failures #91705
Comments
jkoritzinsky
added
blocking-clean-ci
dotnet-issue-labeler
bot
added
the
needs-area-label
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=397220 Error MessageFill the error message using step by step known issues guidance. {
"ErrorMessage": "The remote certificate is invalid because of errors in the certificate chain",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validationBuild: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=397220 Report
Summary
|
vcsjones
removed
the
needs-area-label
|
@lewing this is showing up on the CI dashboard, can you please triage it appropriately? |
|
I don't have any special insight into a certificate error happening on osx/tvos for coreclr and mono other than having seen azdo failures related to ssl/certs before (dotnet/dnceng#1372 dotnet/installer#17588). I would bring it up with engineering services. |
|
@steveisok any infrastructure issues you know of? |
Nothing that I'm aware of |
|
I spot checked the test failures and they don't seem mac-catalyst specific. Also many of these are on 6.0 and 7.0 builds - could be there was a fix in main that needs to be backported? Or something specific to machines used in those servicing branches? |
|
This does not appear to be an infrastructure issue. ie, we're only seeing the failure in dotnet/runtime repo, and it appears to be test specific. 
These failures... 
... all appear to be related (and contained) to a PR Levi Broderick was working on (and not particularly interesting to the investigation). Glancing at the oldest instance of when release/7.0 started failing (just a random spot check)... 
... it looks like that was introduced by 8473eeb. Hope that helps with the search. I'm happy to help further if needed. At the moment, I'm going to close the related "infra" issue I filed. |
lewing
changed the title
|
@jeffhandley looks like this might be related to the md5 related changes? |
I am having a hard time understanding how that change may be related to the errors you are seeing here.
|
|
The test failing in the report that I see is In It is not disabled in release 7.0: That test was disabled with #79407. Presumably we just want to backport disabling that test? |
ghost
added
the
in-pr
ghost
removed
the
in-pr
wfurt
added
the
tracking-external-issue
|
I think we can close this. |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=397220
Build error leg or test failing: Build / maccatalyst-x64 Release AllSubsets_Mono / Send to Helix
Pull request: #91646
Error Message
Fill the error message using step by step known issues guidance.
{ "ErrorMessage": "The remote certificate is invalid because of errors in the certificate chain", "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": false }Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=397220
Error message validated:
The remote certificate is invalid because of errors in the certificate chainResult validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/7/2023 12:17:22 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: