Repository navigation
ci: repair TLS failures when publishing test and coverage results #2812
Description
Problem
Azure Pipelines can fail after tests finish because test-result or coverage
publication cannot establish a TLS connection. This blocks PR validation and
can leave named test outcomes unavailable even when the execution log reports
success.
The observed publisher error is
System.Security.Authentication.AuthenticationException /
RemoteCertificateNameMismatch. In two jobs, the test-result publisher also
logged Failed to publish test results despite a successful task badge.
Evidence
All observations use the same target commit,
d3f3af6bd3e4b7d191f51c9eb29f9aeffe788193, on first-attempt jobs.
| PR and job | Execution evidence | Blocking publication |
|---|---|---|
#2808, UnitTests vw |
114/114 passed; all 114 named published results independently verified | Coverage publication failed with TLS hostname mismatch |
#2809, UnitTests train |
Console reports 78/78 passed, no cancellations or aborted suites | Test results were not published; coverage publication failed with the same TLS error |
#2809, RTests lightgbm |
Runtime completed successfully | Test results were not published; coverage publication failed with the same TLS error |
The last row is not a claim that every named R test passed: those outcomes
could not be verified because publication failed. A same-target comparator
without the serializer change published ten passing R LightGBM tests and
showed the same shutdown diagnostic; it is not substituted for the missing
results.
Expected outcome
Investigate the hosted-agent-to-Azure-Pipelines TLS/certificate path, then
retry only the affected publication-failed jobs within the existing retry
budget. Confirm successful coverage publication and complete named test results.
Preserve the original attempts and revision identities.
Do not disable certificate validation, weaken tests, or change AIPrompt/product
code to hide these infrastructure failures. No source-level repair has been
identified yet, so this issue does not propose a speculative code PR.
Activity
github-actions commentedon Nov 5, 2026
Hey Rana Singh (@ranadeepsingh) 👋!
Thank you so much for reporting the issue/feature request 🚨.
Someone from SynapseML Team will be looking to triage this issue soon.
We appreciate your patience.