BQC timeout with coverage data in the Summary

[robesposito]

BQC timeout with coverage data in the summary.

• Extension: BuildQualityChecks
• Environment: Azure DevOps Services (cloud)
• Agent type: Microsoft-hosted
• Pipeline type: yaml pipeline

We are experiencing the problem described in #239. The most recent comment on that issue says:
"If, however, you see coverage data or a status property in the API result and BQC still keeps timing out, open an issue here and send your logs to PSGerExtSupport@microsoft.com."

We are not seeing a status property in the API result, but the coverage is visible in the Summary and Code Coverage tabs. I am sending logs (with System.Debug and BQC.LogRawData set to true) to PSGerExtSupport@microsoft.com.

[ReneSchumacher]

Hi @robesposito,

thank you for sending over the logs and screenshots. I can see that there is no coverage value in the summary (it says 0%), which is a good indicator that something went wrong on the Azure DevOps side. You sent the logs from your .NET test task and BQC. Did you also publish your code coverage using the Publish Code Coverage Results task? If not, that would explain the behavior. The .NET CLI task does not automatically publish coverage data. It just uploads the coverage file as a pipeline artifact, which is enough for the Report Generator to work, but not for the coverage APIs.

[robesposito]

@ReneSchumacher apologies, I now see that the screenshot said 0% for coverage in the Summary. I was looking at the percentage for "Tests" and also saw coverage results in the separate tab, so the title of my ticket is inaccurate. However, I just sent a follow up email with a new screenshot from the same build. Somehow it updated to 25.19% after I took the screenshot. I didn't re-run it and it appeared to already be finished when I took the first screenshot showing 0%.

We are using the .NET Core task to run tests with "publishTestResults: true". My understanding from the Publish Code Coverage Results task documentation is that we don't need the separate Publish task in this case.

Tasks such as Visual Studio Test, .NET Core, Ant, Maven, Gulp, and Grunt also provide the option to publish code coverage data to the pipeline. If you are using these tasks, you do not need a separate Publish Code Coverage Results task in the pipeline.

The .NET Core CLI task documentationfor publishTestResults says:

Use when command = test. Publish test results and code coverage. Default: true.

I'm still a bit confused. Let me know if I can provide additional information.

[lenniehwtw-new]

Re this issue I've got the same issue and have followed the steps on the related issue to get logs.
Before I submit to Azure Devops can you confirm that this API call is ok

##[debug]{"coverageData":[],"build":{"id":"1856210","url":"https://dev.azure.com/rcss-willistowerswatson/_apis/build/Builds/1856210"},"deltaBuild":null,"coverageDetailedSummaryStatus":11}

It is requesting "coverageDetailedSummaryStatus":"11" rather than "coverageDetailedSummaryStatus":"codeCoverageSuccess" as specified in your example.

[lenniehwtw-new]

As recommended I've raised a problem with ADO services and have copied the logs etc to you in an email