[Mesa-dev] [PATCH 2/2] panfrost/ci: Use special runner for LAVA jobs

[Tomeu Vizoso]

So repositories don't need to be specially configured with a token to
access LAVA, store this token in a bind volume for a special runner.

Signed-off-by: Tomeu Vizoso <tomeu.vizoso at collabora.com>
---
 src/gallium/drivers/panfrost/ci/gitlab-ci.yml | 10 +---------
 1 file changed, 1 insertion(+), 9 deletions(-)

diff --git a/src/gallium/drivers/panfrost/ci/gitlab-ci.yml b/src/gallium/drivers/panfrost/ci/gitlab-ci.yml
index 6cbdd134b1c3..9be47935e77e 100644
--- a/src/gallium/drivers/panfrost/ci/gitlab-ci.yml
+++ b/src/gallium/drivers/panfrost/ci/gitlab-ci.yml
@@ -148,19 +148,11 @@ build:arm64:
 .test:
   stage: test
   tags:
-    - idle-jobs
+    - idle-lava
   image: $CI_REGISTRY_IMAGE/debian/$DEBIAN_VERSION:arm64-${IMAGE_TAG}  # Any of the images will be fine
   variables:
     GIT_STRATEGY: none # no need to pull the whole tree for submitting the job
   script:
-    - mkdir -p ~/.config/
-    - |
-      echo "default:
-        uri: https://lava.collabora.co.uk/RPC2
-        timeout: 120
-        username: jenkins-fdo
-        token: $LAVA_TOKEN
-      " > ~/.config/lavacli.yaml
     - lava_job_id=`lavacli jobs submit $CI_PROJECT_DIR/results/lava-deqp.yml`
     - echo $lava_job_id
     - lavacli jobs logs $lava_job_id | grep -a -v "{'case':" | tee results/lava-deqp-$lava_job_id.log
-- 
2.20.1