On Wed, Aug 27, 2008 at 2:18 PM, Paul Vriens <[EMAIL PROTECTED]> wrote: > James Hawkins wrote: >> >> On Wed, Aug 27, 2008 at 11:40 AM, Adam Petaccia <[EMAIL PROTECTED]> >> wrote: >>> >>> On Wed, 2008-08-27 at 10:26 +0200, Paul Vriens wrote: >>>> >>>> Hi, >>>> >>>> I was looking into the recent test failures for the msi/package tests on >>>> my >>>> WinXP box. >>>> >>>> The reason for most of them was a stray MSITEST package that couldn't be >>>> removed >>>> via the 'Add/Remove Programs' (had to remove stuff from the registry). >>>> >>>> Any one else seeing this? (Adam Petaccia's XP box has the same issue I >>>> guess). >>>> >>> I can provide any details you need about the XP box, the first thing I >>> can think of is that the user running the tests is an administrator. >>> >> >> That's not why the tests are failing. The install tests are timing >> out, and if the winetest executable kills the child process that it >> believes is 'hung', then you're killing the installer process midway >> through an install and thus leaving the system in a broken state. >> > So were back to fixing the timeouts. > > I double checked again and can't see any logging enabled (checked the > registry keys your provided). >
Of course; there are tons of tests. The timeout needs to be extended, at least for install.c. -- James Hawkins