From: Daniel Stone <daniels@collabora.com>
Date: Fri, 10 Mar 2023 13:38:30 +0000 (+0000)
Subject: ci/android: Use a more aggressive timeout for the job
X-Git-Tag: upstream/23.3.3~11835
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=e61d022313a06e058e2585735c5d2daebe959d96;p=platform%2Fupstream%2Fmesa.git

ci/android: Use a more aggressive timeout for the job

This job sometimes - very, very, rarely - fails to start Cuttlefish,
the Android VM environment. Given that we don't have any structural
monitoring and restarting (unlike LAVA/BM/B2C) for this, just stick a
more aggressive timeout on the job, so it'll be retried if it fails to
start.

Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21837>
---

diff --git a/.gitlab-ci/test/gitlab-ci.yml b/.gitlab-ci/test/gitlab-ci.yml
index 7579990..dd5a7aa 100644
--- a/.gitlab-ci/test/gitlab-ci.yml
+++ b/.gitlab-ci/test/gitlab-ci.yml
@@ -65,6 +65,7 @@ rustfmt:
       artifacts: false  # The Android build will be downloaded later
     - job: debian/x86_test-android
       artifacts: false
+  timeout: 20m
   script:
     - ./install/cuttlefish-runner.sh
   artifacts: