Re: Unknown issue with test.winehq.org

2007-03-01 Thread Paul Vriens
Peter Oberndorfer wrote: On Thursday 01 March 2007 08:30, Paul Vriens wrote: Alexandre Julliard wrote: Paul Vriens <[EMAIL PROTECTED]> writes: exception: 42 tests executed (0 marked as todo, 0 failures), 0 skipped. exception: 279 tests executed (0 marked as todo, 5 failures), 0 skipped. The

Re: Unknown issue with test.winehq.org

2007-03-01 Thread Peter Oberndorfer
On Thursday 01 March 2007 08:30, Paul Vriens wrote: > Alexandre Julliard wrote: > > Paul Vriens <[EMAIL PROTECTED]> writes: > > > >> exception: 42 tests executed (0 marked as todo, 0 failures), 0 skipped. > >> exception: 279 tests executed (0 marked as todo, 5 failures), 0 skipped. > >> > >> The f

Re: Unknown issue with test.winehq.org

2007-02-28 Thread Paul Vriens
Alexandre Julliard wrote: Paul Vriens <[EMAIL PROTECTED]> writes: exception: 42 tests executed (0 marked as todo, 0 failures), 0 skipped. exception: 279 tests executed (0 marked as todo, 5 failures), 0 skipped. The first one triggers the 'end of this test' in dissect. The second one is thus no

Re: Unknown issue with test.winehq.org

2007-02-28 Thread Alexandre Julliard
Paul Vriens <[EMAIL PROTECTED]> writes: > exception: 42 tests executed (0 marked as todo, 0 failures), 0 skipped. > exception: 279 tests executed (0 marked as todo, 5 failures), 0 skipped. > > The first one triggers the 'end of this test' in dissect. The second > one is thus not accepted as dissec

Re: Unknown issue with test.winehq.org

2007-02-28 Thread Paul Vriens
Paul Vriens wrote: Hi, So finally we have a working winetest executable and the test.winehq.org scripts should be able to handle the new reports. Could someone have a look what the issue currently is on the webserver as I've sent several reports (a few hours ago) and they are not handled ye

Unknown issue with test.winehq.org

2007-02-28 Thread Paul Vriens
Hi, So finally we have a working winetest executable and the test.winehq.org scripts should be able to handle the new reports. Could someone have a look what the issue currently is on the webserver as I've sent several reports (a few hours ago) and they are not handled yet? Cheers, Paul.