https://bugs.winehq.org/show_bug.cgi?id=31787
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED
--- Comment #4 from François Gouget fgouget@codeweavers.com --- This is done.
* The Missions VM filed allows specifying what a Wine VM will be testing: pure win32 build, Windows on Windows from either the 32 bit or 64 bit side, whether only indirectly impacted tests should be retested, etc.
* And the submission page now allows picking the build (win32, wow32 or wow64) in which to run the tests, as well as the locale.
* The task timeout is computed based on how much work there will be (rebuilding a single test or rebuilding all of Wine because of a global header change).
* CheckForWinetestUpdate deals with creating the relevant Wine VM jobs and the priority of the Wine VM update job (high) is decoupled from that of the update the WineTest results job (low).