From 634b77edad6c32c101f3e5daea6a5ffc0c83d904 Mon Sep 17 00:00:00 2001 From: Nick Volynkin Date: Mon, 11 Aug 2025 11:04:33 +0300 Subject: [PATCH] [ci] Continue application tests after one of them fails The purpose of this change is to: 1. Provide more information to the developer who goes to look at CI results. 2. Help CI workflows complete faster, taking into account that we often restart these workflows. Default strategy is `fail-fast: true`, so when one of app test fails, all running jobs are canceled. This way we don't know if they would succeed or not. And when we restart them, all progress is lost. Reference: * https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations#handling-failures * https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idstrategyfail-fast Signed-off-by: Nick Volynkin --- .github/workflows/pull-requests.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/pull-requests.yaml b/.github/workflows/pull-requests.yaml index 8563bd40..d8659636 100644 --- a/.github/workflows/pull-requests.yaml +++ b/.github/workflows/pull-requests.yaml @@ -269,6 +269,7 @@ jobs: test_apps: strategy: + fail-fast: false matrix: ${{ fromJson(needs.detect_test_matrix.outputs.matrix) }} name: Test ${{ matrix.app }} runs-on: [self-hosted]