From 68a84f6535de738a71efd9d413ca43371d165219 Mon Sep 17 00:00:00 2001 From: Eli Schwartz Date: Tue, 1 Nov 2022 15:06:13 -0400 Subject: fix confusing azure pipelines status for coverage The coverage report was always the final section of the main test run. This made it hard to scroll around and find exactly what went wrong -- particularly as not everyone realizes that coverage isn't part of the test run, but also because the output from coverage is... excessively long. This mirrors what we do in our other workflows. --- azure-pipelines.yml | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'azure-pipelines.yml') diff --git a/azure-pipelines.yml b/azure-pipelines.yml index 998d035..ba5b28e 100644 --- a/azure-pipelines.yml +++ b/azure-pipelines.yml @@ -112,3 +112,8 @@ jobs: filePath: .\ci\run.ps1 env: MESON_CI_JOBNAME: azure-$(System.JobName) + - task: PowerShell@2 + displayName: Gathering coverage report + inputs: + targetType: 'filePath' + filePath: .\ci\coverage.ps1 -- cgit v1.1