Helix SDK failing to post test results to azure devops
See original GitHub issueSeeing various reports of failures when POSTing test runs to the URL: https://dev.azure.com/dnceng/public/_apis/test/runs?api-version=5.0-preview.2
which is manifesting in 503 errors:
F:\workspace\_work\1\s\.packages\microsoft.dotnet.helix.sdk\2.0.0-beta.19463.3\tools\azure-pipelines\AzurePipelines.MultiQueue.targets(16,5): error : Request to https://dev.azure.com/dnceng/public/_apis/test/runs?api-version=5.0-preview.2 returned failed status 503 Service Unavailable [F:\workspace\_work\1\s\tests\helixpublishwitharcade.proj]
F:\workspace\_work\1\s\.packages\microsoft.dotnet.helix.sdk\2.0.0-beta.19463.3\tools\azure-pipelines\AzurePipelines.MultiQueue.targets(16,5): error : [F:\workspace\_work\1\s\tests\helixpublishwitharcade.proj]
F:\workspace\_work\1\s\.packages\microsoft.dotnet.helix.sdk\2.0.0-beta.19463.3\tools\azure-pipelines\AzurePipelines.MultiQueue.targets(16,5): error : {"$id":"1","innerException":null,"message":"TF10216: Azure DevOps services are currently unavailable. Try again later. Activity Id: 492fec1d-55ee-47f2-8853-0f26bdefb63d","typeName":"Microsoft.VisualStudio.Services.CircuitBreaker.CircuitBreakerShortCircuitException, Microsoft.VisualStudio.Services.Common","typeKey":"CircuitBreakerShortCircuitException","errorCode":0,"eventId":3000} [F:\workspace\_work\1\s\tests\helixpublishwitharcade.proj]
##[error].packages\microsoft.dotnet.helix.sdk\2.0.0-beta.19463.3\tools\azure-pipelines\AzurePipelines.MultiQueue.targets(16,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Request to https://dev.azure.com/dnceng/public/_apis/test/runs?api-version=5.0-preview.2 returned failed status 503 Service Unavailable
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Publishing test results to Azure DevOps doesn't support retry
However if it fails once, the test cases that failed are published to AzureDev Ops as failed, then they are not updated, so...
Read more >Azure Devops: Yes! You should publish your test results ...
Azure Devops : Yes! You should publish your test results even if they fail!
Read more >Azure DevOps unit test result not being published
Hello community Since a few days we are facing a weird issue on Azure DevOps, regarding our unit test results; some of them...
Read more >Failed Tests in DevOps Pipeline due to "could not find ...
Hi , I am facing the below issue while deploying my Azure Functions. There are tests written in the pipeline which are failing...
Read more >Review test results - Azure Pipelines
Review continuous test results with a build or release pipeline in Azure Pipelines or Team Foundation Server (TFS)
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the info. Should we nevertheless switch to the non preview api endpoint?
Thanks