Hi all,
recently the set of VMs suggested to run the tests on by default has changed. It no more includes NT4, XP and Vista (although it does include win2000), 32-bit VMs for NT4, XP and Vista don't even exist in the list of available VMs (64-bit XP and Vista do exist, but for some reason are not used).
Is there a reason for that?
On Fri, 12 Apr 2013, Dmitry Timoshkov wrote:
Hi all,
recently the set of VMs suggested to run the tests on by default has changed. It no more includes NT4, XP and Vista (although it does include win2000), 32-bit VMs for NT4, XP and Vista don't even exist in the list of available VMs (64-bit XP and Vista do exist, but for some reason are not used).
Is there a reason for that?
I assume you mean on https://testbot.winehq.org/ which is the old WineTestBot. If so then the reason is that a bunch of VMs appear to be on a host for which the VMware license expired (my guess) which means they can no longer be used.
So to avoid having essentially every job stuck in the 'running' state indefinitely (the symptom of this particular failure mode), I marked them as offline and the WineTestBot no longer lets you schedule jobs on them.
I'd point you to the new WineTestBot but it does not have NT4 and Windows 2000 VMs if you were specifically looking for those.
It does have shinny Windows 8 VMs with tons of test failures though. Ain't that enticing!?
Francois Gouget fgouget@codeweavers.com wrote:
recently the set of VMs suggested to run the tests on by default has changed. It no more includes NT4, XP and Vista (although it does include win2000), 32-bit VMs for NT4, XP and Vista don't even exist in the list of available VMs (64-bit XP and Vista do exist, but for some reason are not used).
Is there a reason for that?
I assume you mean on https://testbot.winehq.org/ which is the old WineTestBot.
Yes, that's what I meant, since apparently it's still an officially used one.
If so then the reason is that a bunch of VMs appear to be on a host for which the VMware license expired (my guess) which means they can no longer be used.
So to avoid having essentially every job stuck in the 'running' state indefinitely (the symptom of this particular failure mode), I marked them as offline and the WineTestBot no longer lets you schedule jobs on them.
As I've pointed out, 64-bit XP and Vista VMs do exist and work just fine, please include at least them in the default VM set.
I'd point you to the new WineTestBot but it does not have NT4 and Windows 2000 VMs if you were specifically looking for those.
Same for win2000 VMs, they exist and work just fine. I asked about NT4 since it was used before and it's nice to have to see what APIs don't exist on that platform.
It does have shinny Windows 8 VMs with tons of test failures though. Ain't that enticing!?
Probably for someone with a lot of free time on their hands, that person definitely is not me.
On Sat, 13 Apr 2013, Dmitry Timoshkov wrote: [...]
As I've pointed out, 64-bit XP and Vista VMs do exist and work just fine, please include at least them in the default VM set.
I see. I have moved WXPX64 and WVISTAX64 to the base set of VMs.
I'd point you to the new WineTestBot but it does not have NT4 and Windows 2000 VMs if you were specifically looking for those.
Same for win2000 VMs, they exist and work just fine. I asked about NT4 since it was used before and it's nice to have to see what APIs don't exist on that platform.
W2KPROSP4 is a base VM so as far as I can tell Windows 2000 is covered.
However both NT4 VMs (WNT4WSSP6 and WNT4SRVSP6) are dead.
Francois Gouget fgouget@codeweavers.com wrote:
On Sat, 13 Apr 2013, Dmitry Timoshkov wrote: [...]
As I've pointed out, 64-bit XP and Vista VMs do exist and work just fine, please include at least them in the default VM set.
I see. I have moved WXPX64 and WVISTAX64 to the base set of VMs.
I still need to manually enable WXPX64 and WXPPROSP2 when I send a test to testbot.
On Wed, 17 Apr 2013, Dmitry Timoshkov wrote: [...]
I still need to manually enable WXPX64 and WXPPROSP2 when I send a test to testbot.
I thought I had switched them to base already but maybe not. I did so again yesterday and rechecked today and it looks like it's ok now.
-
Dmitry Timoshkov -
Francois Gouget