2010/4/12 Greg Geldorp <[email protected]>: > I'm happy to announce that WineTestBot (http://winetestbot.geldorp.nl) is now > actively scanning wine-patches submissions for changes to tests. If it finds > a test change, it will apply the changes, build the affected test executables > and run them on the base VMs. Results will be mailed back to the submitter. > It will also try to determine if new failures were introduced, by comparing > the test results to the most recent run using winetest.exe from WineHQ. If it > thinks there are new failures, a message is sent to the author with a copy to > wine-devel. > > The bot will only process complete series, so it will queue up patches that > appear to be part of a series. Then when the series is complete, it generates > one big patch file by adding all the individual patches from the series > together before submitting it. We'll have to see how robust this is, it is > quite possible to mess up this algorithm. > > Only patches that contain changes to tests are run. It checks to see if any > dlls/<dllname>/tests/* files were changed, if so it is deemed a change to the > tests. This should cover most cases, but again is not 100% correct all the > time (if you only change a file in include/ then the tests depending on the > header files don't get run). In the end we still have the daily run that's > done when Alexandre publishes a new winetest.exe. > > There's a new item in the WineTestBot menu, "Wine-patches". It will show > which patches have been received via the mailing list and what the bot has > done with them. > > Of course, you'll still be able to manually submit a patch to the bot too. > These run at higher priority than the jobs generated from wine-patches > submissions. > > Happy testing, Ge. > > > >
Hi Greg, Perhaps you could also check for programs/<programname>/tests/ now that at least cmd has tests. WineTestBot is a wonderful tool, thanks for supporting and improving it! -- Nicolas Le Cam
