On Fri, 20 Oct 2023, Eric Pouech wrote:
[...]

I've tried to repro a couple of them locally, recreating the docker image with
the docker script... to no avail

I have a question on that subject: how do you run the Wine tests in your 
local docker image?

The reason I ask is that reproducing GitLab CI's container and using it 
for builds is pretty easy. But running the tests in it requires starting 
X and the commands (in test.yml) for that are not directly usable 
outside the GitLab environment.

So do you copy/paste all the xinitrc, startx, wine-mono & co stuff to a 
script, append the ./wine command you want to run at the end and do 
something like "docker run gitlab-debian12 ./myscript"?

yes something along these lines [2]

- mounting build directory

- mounting script directory (with some of the scripts being a direct copy of tools/gitlab, others being a more or less equivalent transformations of the .yml files into bash scripts)

- actually split in stages (create image + install wine & deps, compile wine (optionnaly with SHA1+fetch+rebase), run winetest (with options for the tests to be run)

pitfalls:

- not using the exact same scripts as the gitlab ones...

- can't get official docker image from gitlab's repo (so a new one is built from docker repo for debian image)

- not running on the exact same OS as the HW used for gitlab's pipeline (which I don't even know the version... so didn't go to the point of spinning a debian vm to run docker on it...)

- is gitlab applying some other parameters when running image (memory limit, swap limit???). idk

my initial goal wasn't to be able to run it regularly, but mainling to try to replicate pipeline failures, which I couldn't get to that point

discrepancies could come from pitfalls above

[1] Why ask me? Am I the GitLab CI maintainer now?

[2] What are the implications of answering?