Recent msi/package tests failures
paul.vriens.wine at gmail.com
Thu Sep 4 00:50:19 CDT 2008
Austin English wrote:
> On Tue, Sep 2, 2008 at 12:45 AM, Paul Vriens <paul.vriens.wine at gmail.com> wrote:
>> James Hawkins wrote:
>>> On Mon, Sep 1, 2008 at 8:08 PM, James Mckenzie
>>> <jjmckenzie51 at earthlink.net> wrote:
>>>> One file per run is all that should be created, IMHO.
>>> No, zero log files should be created. This discussion is about
>>> reducing the time it takes to run the tests, and any logging hinders
>>> that effort.
>> OK, back to the initial discussion then.
>> I did find that 'System Restore' was the cause of the slowdown on a lot of (at
>> least) XP and Vista systems. Patches are being sent for that.
>> Disabling logging as I suggested at first only helps to get rid of a few seconds
>> from the total run time of these tests. The question remains however why some
>> people have loads of log files in their temp directory and some don't.
>> Do you think that for testing purposes we could add a check in the install tests
>> that shows us the number of MSI logfiles in the temp directory before and
>> afterwards? Or is it enough that several people already responded to my question
>> about those logfiles?
> FWIW, my work XP box times out on quite a few tests, but has system
> restore disabled.
Yes, the same happens to other boxes when looking at test.winehq.org. 'System
Restore' is definitely one of the causes but we are not there yet.
The other (non msi) timeouts are most likely not influenced by the system
restore facility but have to be fixed as well (most noticeably dplayx).
More information about the wine-devel