On Thu, 25 Oct 2007, James Hawkins wrote: [...]
I don't think that's fair to long tests, say msi:install.
I don't think we have any long-running tests right now (except the 'ftp' tests but that's probably a bug). All the tests that time out do so because they do stuff that pops up a MessageBox and thus blocks them indefinitely.
msi:install is no exception. I can now confirm that when I run it on Windows 98 I get firt a MessageBox telling me that:
Service 'TestService' (TestService) could not be installed. Verify that you have sufficient privileges to install system services.
And then a MessageBox telling me that it crashed:
This program has performed an illegal operation and will be shut down.
MSI_TEST caused an invalid page fault in module <unknown> at 0000:00000009. Registers: EAX=00b2f7e0 CS=015f EIP=00000009 EFLGS=00010297 EBX=0046a9b3 SS=0167 ESP=00b2f778 EBP=00b2fd78 ECX=f8294700 DS=0167 ESI=0046a198 FS=0fcf EDX=005800a8 ES=0167 EDI=00000711 GS=0000 Bytes at CS:EIP: 00 1f 05 65 04 70 00 65 04 70 00 54 ff 00 f0 d4 Stack dump: 00000167 00436173 00b2f7e0 00000000 00000002 0046a9c8 00b2f7a8 00b2f7cc 01020102 01020102 01020102 01020102 ffffffff 0000000b 00000009 00000008
So I think it's premature to devise schemes for skipping long tests. If anything the duration of 'make test' is more likely to explode due to the accumulation of individual tests (already more than 300), rather than due to a single test taking a long time.