Regression testing of Windows binaries is done via wine.
There are some issues: we see error messages like
0070:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0070:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
0070:err:systray:initialize_systray Could not create tray window
Apparently, we need to tell wine explicitly that we don't need graphics stuff.
The error messages from wine then get reported as red dots on the snapshots page (like real regression failures).
I am not a wine expert, but from what I've read on similar issues, we probably want to do the testing using the "wineconsole" command instead of "wine" to fix this.
In [r13344], I tried to change the command from win/wine64 to wineconsole.
Related
Commit: [r13344]
According to the Wine User's Guide, wineconsole should not be needed for our use-case. As long as the program does not try to create a Window, plain wine should just work using stdio Unix streams.
So the question becomes: what is trying to create a window here?