diff options
| author | Eli Schwartz <eschwartz@archlinux.org> | 2022-11-01 15:06:13 -0400 |
|---|---|---|
| committer | Eli Schwartz <eschwartz@archlinux.org> | 2022-11-16 19:28:24 -0500 |
| commit | 68a84f6535de738a71efd9d413ca43371d165219 (patch) | |
| tree | cc075e2683e2a4384270fe577c2516939a132891 /azure-pipelines.yml | |
| parent | 47d1a55e780f928c9c1613220d6267de530e64b4 (diff) | |
| download | meson-68a84f6535de738a71efd9d413ca43371d165219.zip meson-68a84f6535de738a71efd9d413ca43371d165219.tar.gz meson-68a84f6535de738a71efd9d413ca43371d165219.tar.bz2 | |
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.
Diffstat (limited to 'azure-pipelines.yml')
| -rw-r--r-- | azure-pipelines.yml | 5 |
1 files changed, 5 insertions, 0 deletions
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 |