On Tue Feb 3 11:47:04 2026 +0000, Matteo Bruni wrote:
Some audio tests already use `WINETEST_INTERACTIVE`. That option is supposed to mean something different, of course, but it might be worth considering if (ab)using the existing option could be preferable. Also, kinda related, do the existing mmdevapi `WINETEST_INTERACTIVE == 1` tests work properly? Are they still useful? I suppose that "interactive" tests are supposed to require user interaction, so are not suited for an automated run, and I would like my extended tests to still be run in an automated setting, even if not for each single MR. So I would consider it inconvenient to reuse `WINETEST_INTERACTIVE` for that. OTOH what benefit would we have from conflating the two concepts? It doesn't look like checking another environment variable is particularly expensive.
I don't know much about the interactive tests, and as I argues that seems something independent from this MR, so I don't have much to comment about that. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9694#note_128622