From 81e0ac6b5dcbd5a09d3ed7e4ad6e4b2f56b5b007 Mon Sep 17 00:00:00 2001 From: Peter Collins Date: Wed, 9 Aug 2023 17:03:00 -0400 Subject: [PATCH] [ci] Report when dotnet-test-slicer fails Changes to the `dotnet-test-slicer` task from commit a4276880 may have caused it to fail silently if any issues occur. Updating the task to fail if anything is written to stderr should fix this. --- .../automation/yaml-templates/run-sliced-nunit-tests.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/build-tools/automation/yaml-templates/run-sliced-nunit-tests.yaml b/build-tools/automation/yaml-templates/run-sliced-nunit-tests.yaml index 45bd0beb9fd..5e44373d5dd 100644 --- a/build-tools/automation/yaml-templates/run-sliced-nunit-tests.yaml +++ b/build-tools/automation/yaml-templates/run-sliced-nunit-tests.yaml @@ -15,6 +15,7 @@ steps: --total-slices=$(System.TotalJobsInPhase) --outfile="${{ parameters.testAssembly }}.runsettings" displayName: Slice unit tests with filter + failOnStderr: true - ${{ else }}: - pwsh: >- dotnet-test-slicer slice @@ -23,6 +24,7 @@ steps: --total-slices=$(System.TotalJobsInPhase) --outfile="${{ parameters.testAssembly }}.runsettings" displayName: Slice unit tests + failOnStderr: true - ${{ if eq(parameters.retryFailedTests, 'false') }}: # If we aren't using auto-retry logic, then this is just a simple template call