From 445ff2e500f2f9d6c4892bdec45492a8894868f2 Mon Sep 17 00:00:00 2001 From: Erik Faye-Lund Date: Wed, 11 Dec 2024 12:23:55 +0100 Subject: [PATCH] panvk/ci: update g52-vk-full job On a single runner, this job currently times out due to taking over 5 hours. The estimate from dEQP runner itself suggests a full run might take over 8 hours with the current configuration. We can't really work with that long runs, even if they are manual. We currently have 7 vim3 runners, so we can actually afford to parallelize the run a bit, to make this a bit more manageable. If we choose 4, we take up a bit more than half of the runners, but we leave two runners (plus a spare) for the pre-merge CI. With this, a each job takes about 2.5 hours. We leave the timeout at 3 hours for now, to have some headroom for new tests being enabled. Acked-by: Daniel Stone Part-of: --- src/panfrost/ci/gitlab-ci.yml | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/src/panfrost/ci/gitlab-ci.yml b/src/panfrost/ci/gitlab-ci.yml index 355d5f41e80..b9bb657cabf 100644 --- a/src/panfrost/ci/gitlab-ci.yml +++ b/src/panfrost/ci/gitlab-ci.yml @@ -347,17 +347,14 @@ panfrost-g52-vk:arm64: HWCI_START_WESTON: 1 panfrost-g52-vk-full:arm64: - # Only allow one runner as we don't have many VIM3 around. - parallel: null + parallel: 4 extends: - panfrost-g52-vk:arm64 - .panfrost-vk-manual-rules - # A full run takes around 4 hours and a half locally on a VIM3 that is thermal throttling. - # We assume worst case scenario (throttling + new faults) - timeout: 5h + timeout: 3h variables: DEQP_SUITE: panfrost-g52-vk-full - JOB_TIMEOUT: 300 + JOB_TIMEOUT: 185 panfrost-g52-piglit-gles2:arm64: extends: