--- Alex Ionescu ionucu@videotron.ca wrote:
Actually, Steven has been doing work on forwarding me the bugs, and I've been fixing them ;) I'm handling this on a case-by-case basis, but we are currently working on a system called SIN, which is a Continous Integration System. Casper is leading the project, but it allows us to automatically compile builds to ensure that the latest commit doesn't break it (in which case it will be automatically removed). A large number of us (especially Steven and I) want to make SIN also actually boot the image in an emulator, and then run automated winetests. This is currently being disputed, since we cannot possibly do this for every build, it would slow down the process too much. One of the suggestions was to do this only X builds, but I'm not sure if that comprise has been approved yet. Defintely, I think you don't have this problem in WINE, since you can easily execute WINE in the compiler environment without requiring booting from an image in an emulator. But we're working on it! We've even thrown the idea of User-Mode ReactOS on the table.
I think it might be possible to do it with QEMU if we accept that we can't run all of the tests to start with. User32,Gdi32,kernel32,ntdll and advapi32 are the most important ones to start with. I expect Winetest can run tests for those dlls in less than 2 mins. We can embrace and extend the Winehq winetest data page a bit and host a page on ReactOS.org to track builds by revision rather than just date.
Thanks Steven
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com