mesa/src/virtio/ci/gitlab-ci.yml
Yiwei Zhang 1af2f5e198 ci: re-enable venus ci
Skip dEQP-VK.binding_model.mutable_descriptor.multiple_arrays_mixed.*
because lavapipe behind venus can end up returning OODM for device
memory allocations.

The instability likely started from lavapipe gaining support of dma-buf
import/export. Then vkr renderer would no longer use the opaque fd
export with lavapipe, and we are hitting certain bottleneck of udmabuf.

Let's get venus ci re-enabled now and we can later flip vkr back to
prefer opaque fd export if seeing lavapipe for comparison.

Signed-off-by: Yiwei Zhang <zzyiwei@chromium.org>
Acked-by: Daniel Stone <daniel.stone@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30356>
2024-07-24 22:25:23 +00:00

26 lines
585 B
YAML

include:
- local: 'src/virtio/ci/gitlab-ci-inc.yml'
venus-lavapipe:
extends:
- .deqp-test
- .venus-lavapipe-test
timeout: 25m
variables:
DEQP_FRACTION: 60
DEQP_SUITE: venus
GPU_VERSION: venus
LP_NUM_THREADS: 2
CROSVM_MEMORY: 12288
CROSVM_CPU: $FDO_CI_CONCURRENT
FLAKES_CHANNEL: "#virgl-ci"
script:
- ./install/crosvm-runner.sh ./install/deqp-runner.sh
venus-lavapipe-full:
extends:
- venus-lavapipe
- .venus-manual-rules
timeout: 3h
variables:
DEQP_FRACTION: 6 # 1 would take 12h so this is as close as we can get