From bb01b10a27a5a0d7bf5a7193fb27cd9dad18274d Mon Sep 17 00:00:00 2001
From: Jon Turney <jon.turney@dronecode.org.uk>
Date: Thu, 8 Nov 2018 23:58:34 +0000
Subject: azure: Simplify how we always publish test results

Use a more concise way of always publishing test results, even when
tests failed
---
 ci/azure-steps.yml | 11 ++---------
 1 file changed, 2 insertions(+), 9 deletions(-)

(limited to 'ci')

diff --git a/ci/azure-steps.yml b/ci/azure-steps.yml
index db532c81c..8bd8c76c1 100644
--- a/ci/azure-steps.yml
+++ b/ci/azure-steps.yml
@@ -111,28 +111,21 @@ steps:
 
      python run_tests.py --backend $(backend)
 
-     echo "##vso[task.setvariable variable=test_status]$LastExitCode"
-
-  continueOnError: true
-
 - task: PublishTestResults@2
   inputs:
     testResultsFiles: meson-test-run.xml
     testRunTitle: $(System.JobName)
     publishRunAttachments: true
+  condition: not(canceled())
 
 - task: CopyFiles@2
   inputs:
     contents: 'meson-test-run.*'
     targetFolder: $(Build.ArtifactStagingDirectory)
+  condition: not(canceled())
 
 - task: PublishBuildArtifacts@1
   inputs:
     artifactName: $(System.JobName)
   # publishing artifacts from PRs from a fork is currently blocked
   condition: eq(variables['system.pullrequest.isfork'], false)
-
-- powershell: |
-     # after publishing test results, even if some failed
-     # exit with the test status
-     exit $(test_status)
-- 
cgit v1.2.3