turnip: set VFD_INDEX_OFFSET in 3D clear/blit path
[mesa.git] / .gitlab-ci / deqp-freedreno-a630-skips.txt
index 65d340c368767fb982eef04b0ea30dff98a70ae1..6007aeb4e20f9b488f9eea25457be11c632c1d9a 100644 (file)
@@ -10,20 +10,70 @@ dEQP-GLES[0-9]*.stress.*
 dEQP-GLES[0-9]*.functional.flush_finish.*
 
 # Unstable test results
-dEQP-GLES3.functional.fragment_out.random.*
-dEQP-GLES3.functional.transform_feedback.*
+#dEQP-GLES3.functional.fragment_out.random.*
+dEQP-GLES3.functional.transform_feedback.*points.*
+dEQP-GLES3.functional.transform_feedback.*lines.*
 dEQP-GLES31.functional.primitive_bounding_box.*
-dEQP-GLES31.functional.layout_binding.ssbo.fragment_binding_array.*
+#dEQP-GLES31.functional.layout_binding.ssbo.fragment_binding_array.*
 
-# Seen a couple flakes on this one.  Note that valgrind complains about
-# some things in deqp reference renderer on this one.  Not sure if that
-# is a real problem or perhaps valgrind gets confused about unitialized
-# z24 channel in z24s8??  Let's just skip this one for now:
-dEQP-GLES3.functional.fbo.msaa.2_samples.stencil_index8
+# Intermittent timeout
+dEQP-GLES31.functional.ssbo.layout.random.all_shared_buffer.23
+dEQP-GLES31.functional.ssbo.layout.random.all_shared_buffer.48
 
-# Two reports of spurious failures on unrelated MRs (2019-09-27, 2019-10-05)
-dEQP-GLES3.functional.texture.specification.texsubimage2d_pbo.r16ui_2d
+# Flakes reported more than once during Jan-Feb 2020
+dEQP-GLES31.functional.layout_binding.ssbo.fragment_binding_array
+dEQP-GLES3.functional.fragment_out.random.0
+dEQP-GLES3.functional.fragment_out.random.1
+dEQP-GLES3.functional.fragment_out.random.12
+dEQP-GLES3.functional.fragment_out.random.13
+dEQP-GLES3.functional.fragment_out.random.17
+dEQP-GLES3.functional.fragment_out.random.24
+dEQP-GLES3.functional.fragment_out.random.27
+dEQP-GLES3.functional.fragment_out.random.28
+dEQP-GLES3.functional.fragment_out.random.32
+dEQP-GLES3.functional.fragment_out.random.34
+dEQP-GLES3.functional.fragment_out.random.35
+dEQP-GLES3.functional.fragment_out.random.36
+dEQP-GLES3.functional.fragment_out.random.40
+dEQP-GLES3.functional.fragment_out.random.44
+dEQP-GLES3.functional.fragment_out.random.47
+dEQP-GLES3.functional.fragment_out.random.5
+dEQP-GLES3.functional.fragment_out.random.50
+dEQP-GLES3.functional.fragment_out.random.51
+dEQP-GLES3.functional.fragment_out.random.55
+dEQP-GLES3.functional.fragment_out.random.58
+dEQP-GLES3.functional.fragment_out.random.59
+dEQP-GLES3.functional.fragment_out.random.61
+dEQP-GLES3.functional.fragment_out.random.63
+dEQP-GLES3.functional.fragment_out.random.66
+dEQP-GLES3.functional.fragment_out.random.67
+dEQP-GLES3.functional.fragment_out.random.69
+dEQP-GLES3.functional.fragment_out.random.70
+dEQP-GLES3.functional.fragment_out.random.71
+dEQP-GLES3.functional.fragment_out.random.80
+dEQP-GLES3.functional.fragment_out.random.82
+dEQP-GLES3.functional.fragment_out.random.86
+dEQP-GLES3.functional.fragment_out.random.88
+dEQP-GLES3.functional.fragment_out.random.91
+dEQP-GLES3.functional.fragment_out.random.93
+dEQP-GLES3.functional.fragment_out.random.95
+dEQP-GLES3.functional.fragment_out.random.96
+dEQP-GLES3.functional.transform_feedback.array_element.interleaved.triangles.highp_mat2x3
+dEQP-GLES3.functional.transform_feedback.array_element.interleaved.triangles.lowp_mat2x4
+dEQP-GLES3.functional.transform_feedback.array_element.separate.triangles.lowp_mat2x4
 
-# Layered rendering is sysmem only and needs working clears
-dEQP-GLES31.functional.geometry_shading.layered.*
-dEQP-GLES31.functional.geometry_shading.instanced.*layer.*
+# Non-sysmem flakes
+dEQP-VK.pipeline.spec_constant.compute.composite.matrix.mat3x2
+
+# Sysmem flake: this one is fairly frequent, but if you enable it then
+# it moves to dEQP-VK.renderpass.dedicated_allocation.attachment.3.393
+#
+#dEQP-VK.renderpass.suballocation.attachment_allocation.grow_shrink.89
+
+# At least some of the separate_channels tests fail on sysmem due to an
+# interaction of use of a UBWC buffer as both a render target and a
+# texture.  Stores are done through both paths in separate channels,
+# and the UBWC updates don't get synced.  The current a650 blob also
+# fails these tests and qcom apparently noted the failure at one point
+# https://gitlab.khronos.org/Tracker/vk-gl-cts/-/issues/2017
+dEQP-VK.renderpass.*separate_channels.*