What to do with tests that run for ages (examples dplayx and msi/install)

[James Hawkins]

On Mon, Aug 4, 2008 at 3:02 PM, Austin English <austinenglish at gmail.com> wrote:
> On Mon, Aug 4, 2008 at 2:57 PM, James Hawkins <truiken at gmail.com> wrote:
>> On Mon, Aug 4, 2008 at 1:03 PM, Paul Vriens <paul.vriens.wine at gmail.com> wrote:
>>> Hi,
>>>
>>> The recent additions to the dplayx tests make these tests run very slow (or
>>> there is just a lot tested?).
>>>
>>> Is there a way to either split up these tests so they don't timeout or better
>>> yet find out if we can run them faster. This issue can be seen on W2K upwards.
>>>
>>> The same can be said about the msi/install tests. This however only seems to be
>>> an issue on XP and Vista.
>>>
>>
>> The install tests should only take forever if you have some form of
>> logging enabled.  All logging should be disabled.
>>
>> --
>> James Hawkins
>>
>>
>>
>
> For me in XP, they repeatedly take forever and usually time out. On my
> 2k box, they run fine. The 2k box is a Pentium 4 single core, and the
> XP box is a Intel duo IIRC. Not sure what logging you're speaking of,
> be it in winetest or in windows itself...
>

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

Debug:DWORD should be 0 or nonexistent
Logging:REG_SZ should be empty or nonexistent

There may be other policies somewhere else that cause logging to
happen.  The tests run fine for me in XP, and for others as well.

-- 
James Hawkins