On Tue Feb 3 11:50:02 2026 +0000, Giovanni Mascellani wrote:
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. Fair enough. I think I was more interested in knowing if anyone ran the interactive tests somewhat recently :sweat_smile:
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/9694#note_128623