A number of tests currently fail in llvmpipe, so the llvmpipe jobs are marked as allowed to fail. Ideally we'll eventually fix our bugs and mark the llvmpipe ones in the tests,
Yeah. Of course that doesn't necessarily need to wait for the rest of the CI bits. :)
Subject: [PATCH 1/2] vkd3d: Filter devices according to VKD3D_VULKAN_DEVICE_FILTER. --- libs/vkd3d/device.c | 35 +++++++++++++++++++++++++++++++---- 1 file changed, 31 insertions(+), 4 deletions(-)
Sure. Please add VKD3D_VULKAN_DEVICE_FILTER to the list of environment variables in the README though. It's perhaps also worth clarifying that VKD3D_VULKAN_DEVICE now applies to the filtered list.
+build32: + stage: build + script: + - ./autogen.sh + - mkdir build + - cd build + - ../configure --enable-demos CFLAGS=-m32 + - make -j$(nproc) + - make -j$(nproc) crosstest + artifacts: + when: always + paths: + - . +
CFLAGS=-m32 doesn't seem ideal, as that implies dropping "-g -O2". I'd suggest CC="gcc -m32", or perhaps something like CFLAGS="-m32 -g -O2".
+# Installing widl from the repositories or compiling Wine with its +# build system would bring in a lot of useless (for us) dependencies, +# easily making the image 1 GB larger; so we just build widl with a +# custom list of gcc calls dumped from an actual Wine build
I think "make tools/widl/widl" should generally do the right thing, without building all of Wine. I'd also be inclined to suggest building a specific widl version like 3.20, instead of building what happens to be in Wine git when creating the image. There may be a similar consideration around targetting unstable instead of a specific release.
Of course widl is also available in the wine64-tools package on Debian. It's a bit unfortunate that this package depends on libwine-dev -> libwine, which ends up pulling in most of Wine's dependencies anyway. Ideally that would be improved on the Debian side, but in theory we could at least do better for the packages hosted at dl.winehq.org...