I see some CI runs fail with this message (e.g. [this run](https://gitlab.winehq.org/bernhardu/wine/-/jobs/164160): ``` ... $ if ($WINETEST_ARGS.count -gt 0) { # collapsed multi-line command Running after_script 00:01 Traceback (most recent call last): File "/home/gitlab-runner/tools/gitlab/virtrunner/qemu-agent.py", line 190, in <module> main() File "/home/gitlab-runner/tools/gitlab/virtrunner/qemu-agent.py", line 179, in main ret = run(virsh, args) File "/home/gitlab-runner/tools/gitlab/virtrunner/qemu-agent.py", line 112, in run print(data.decode("utf-8")) UnicodeDecodeError: 'utf-8' codec can't decode byte 0x9a in position 8638: invalid start byte Uploading artifacts for failed job 00:01 ... ```
The artifact [winetest.log](https://gitlab.winehq.org/bernhardu/wine/-/jobs/164160/artifacts/raw/winetes...) from the example above contains this test failures, where these environment variables do no longer match the parent process: ``` process.c:1327:1.000 Test succeeded process.c:1327:1.015 Test failed: Parent-env string CI_COMMIT_AUTHOR=Bernhard Übelacker bernhardu@mailbox.org isn't in child process process.c:1327:1.421 Test failed: Parent-env string GITLAB_USER_NAME=Bernhard Übelacker isn't in child process process.c:1352:1.687 Test failed: Child-env string CI_COMMIT_AUTHOR=Bernhard sbelacker bernhardu@mailbox.org isn't in parent process process.c:1352:1.687 Test failed: Child-env string GITLAB_USER_NAME=Bernhard sbelacker isn't in parent process ```
I tried to get some more details and [this testbot run](https://testbot.winehq.org/JobDetails.pl?Key=158611&f201=exe64.report#k2...) points to the second CreateProcessA, which is given a specific `child_env` to use for process creation, but does not make it into child process in Windows for some reason.
Therefore this patch is an attempt to filter out these known environment variables.