https://bugs.winehq.org/show_bug.cgi?id=31784
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW
--- Comment #3 from François Gouget fgouget@codeweavers.com --- The central issue with having multiple snapshots per VM is that the WineTestBot needs to realize it cannot start tests in both snapshots at the same time.
However currently the WineTestBot is configured to never start more than one VM per host (4 to 8 cores, 16GB and all that to run just one VM! :-( ). So I thought we could take a shortcut: have two entries in the VMS table both referencing the same domain but different snapshots: win7u domain=wtbw7u snapshot=ie11-wtb-ja win7u-ko domain=wtbw7u snapshot=ie11-wtb-ko
Since we never start more than one VM per host there would be no risk of the WineTestBot trying to run tests in both configurations at the same time. Unfortunately this did not work: for some reason the TestBot got confused resulting in one of the VMs getting stuck in the 'reverting' state while there was no qemu process running on the host.
Possibly while reverting win7u-ko the Engine checked the status of the win7u VM (VMs::UpdateStatus() or VMs::IsPoweredOn()), noticed it was running despite not being supposed to, and shut it down which resulted in the win7u-ko revert process being interrupted.