From 38c5524989a60bf546cb7e1027abb6df2afd7945 Mon Sep 17 00:00:00 2001
From: Nikita Kornev <nikita.kornev@intel.com>
Date: Wed, 10 Apr 2024 14:18:14 +0200
Subject: [PATCH] [CI] Add timeout limit for SYCL-CTS (#13335)

Also add an output to GITHUB_STEP_SUMMARY.
---
 .github/workflows/sycl-linux-run-tests.yml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/.github/workflows/sycl-linux-run-tests.yml b/.github/workflows/sycl-linux-run-tests.yml
index 59f1ad983691..b5ec7bd773f8 100644
--- a/.github/workflows/sycl-linux-run-tests.yml
+++ b/.github/workflows/sycl-linux-run-tests.yml
@@ -307,6 +307,9 @@ jobs:
       if: inputs.tests_selector == 'cts'
       env:
         ONEAPI_DEVICE_SELECTOR: ${{ inputs.target_devices }}
+      # This job takes ~100min usually. But sometimes some test isn't
+      # responding, so the job reaches the 360min limit. Setting a lower one.
+      timeout-minutes: 150
       # By-default GitHub actions execute the "run" shell script with -e option,
       # so the execution terminates if any command returns a non-zero status.
       # Since we're using a loop to run all test-binaries separately, some test
@@ -340,6 +343,7 @@ jobs:
         done
         if [ -n "$status" ]; then
           echo "Failed suite(s): $failed_suites"
+          echo "Failed suite(s): $failed_suites" >> $GITHUB_STEP_SUMMARY
           exit 1
         fi
         exit 0