http://bugs.winehq.org/show_bug.cgi?id=36040
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #3 from Sebastian Lackner sebastian@fds-team.de --- @Josh: How does the wineserver block your test from exiting? Do you start the wineserver explicitly? If yes, you can just pass the -p0 flag. Otherwise it shouldn't block your tests because wineserver acts as a daemon and immediately forks into the background.
If you just want to make sure the wineserver is killed after each test (normally shouldn't be necessary, and will probably be a bit slower than keeping the wineserver persistent for a couple seconds), why not use something like:
wine ./unittest.exe wineserver -k
Of course something like an environment WINE_SERVER_FLAGS would be nice (especially for users that don't want a permanent wineserver, like in comment 1), but I don't see why it should be impossible to have a similar effect with the existing commandline options. Can you probably provide a bit more details?