Publish test results is failing
See original GitHub issueWhen Publish test results
task is trying to upload Junit formatted xml file at that time it is throwing error like Failed to publish test results: Illegal characters in path.
Publish Test Results : version 2.0.1
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:14 (3 by maintainers)
Top Results From Across the Web
Failed to publish test results in release pipeline
We have created a release pipeline to be triggered by azure container registry. As part of the pipeline, we run some junit tests...
Read more >AzureDevops: How to publish test results when tests fail?
I have some unit tests written with jest . Obviously, sometimes they fail. I want to publish the result to the build Test...
Read more >PublishTestResults@2 fails to publish test results to Azure ...
This used to work with Azure DevOps Server 2019. Task logs. Important lines: ##[warning]Failed to publish test results: One or more errors ...
Read more >PublishTestResults@2 - Publish Test Results v2 task
When this boolean's value is true , the task will fail if any of the tests in the results file are marked as...
Read more >Chapter 5 - Publishing Results in Pipeline
But we would like to generate a test report even when our tests are failing, right? So instead, we'll set it to run...
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
Same problem with both versions (v1.* and v2.*). VSTS used. Private build agent. During mailing to devops_tools@microsoft.com receiving following: Couldn’t deliver to the following groups: vscsscomm@microsoft.com, tri@microsoft.com
Closing this issue - we verified that the JUNit XML was not properly formatted resulting in failure.