commit 5585b8eaddd6799b4486a749de18ae9a6f03b91c
author Michel Dänzer <mdaenzer@redhat.com> Tue Dec 03 10:45:28 2019 +0100
committer Michel Dänzer <michel@daenzer.net> Wed Dec 04 10:36:33 2019 +0100
tree 453fe087f6f1a1d7de47d5942a595d9f2915c620
parent ddacd3d43b203e7c66ec366820e2a230b7e3aa67

gitlab-ci: Run piglit glslparser & quick_shader tests separately

And only use --process-isolation false for the quick_gl tests.

This will hopefully avoid variance in the test results that we've been
seeing lately. But even if it doesn't, it should at least help narrow
down the cause of the variance.

Tested-by: Vasily Khoruzhick <anarsoul@gmail.com>
Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>

.gitlab-ci.yml

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index a714ae3..56dce7b 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -489,6 +489,7 @@
   variables:
     LP_NUM_THREADS: 0
     PIGLIT_OPTIONS: >
+      --process-isolation false
       -x arb_gpu_shader5
       -x glx-multithread-clearbuffer
       -x glx-multithread-shader-compile
@@ -496,7 +497,13 @@
       -x maxsize
     PIGLIT_PROFILES: quick_gl
 
-piglit-glslparser+quick_shader:
+piglit-glslparser:
+  extends: .piglit-test
+  variables:
+    LP_NUM_THREADS: 0
+    PIGLIT_PROFILES: glslparser
+
+piglit-quick_shader:
   extends: .piglit-test
   variables:
     LP_NUM_THREADS: 1
@@ -507,8 +514,7 @@
       -x spec@arb_separate_shader_objects@linker
       -x spec@arb_shader_storage_buffer_object@execution
       -x spec@glsl-1.50@execution@built-in-functions
-    PIGLIT_PROFILES: "glslparser quick_shader"
-    PIGLIT_RESULTS: "glslparser+quick_shader"
+    PIGLIT_PROFILES: quick_shader
 
 .deqp-test:
   extends: .test