On Fri, May 31, 2013 at 7:58 AM, Gary Martin <[email protected]>wrote:
> On 30/05/13 18:47, Anze Staric wrote: > >> I have fixed the failing test in bhsearch. Only 2 remain :) >> >> >> Anze >> > > Excellent work! > > We now have a buildslave running some unit tests on commits (with a two > minute tree stabilisation timer). This is certainly not meant to be a > substitute for running the tests locally but it is available for reference. > > There are plenty of improvements that can be made but it would be good to > stop rest of the current tests from failing at which point I will probably > look at getting some kind of notification of changes from success to > failure. > > The recent build list is currently here: http://ci.apache.org/builders/** > bh-unit-tests/ <http://ci.apache.org/builders/bh-unit-tests/> > > As Anze said, the good news is that the most recent complete build shows > both bhsearch and bhrelations as passing all tests that are not skipped. > Multiproduct still has two failed tests (see > http://ci.apache.org/builders/**bh-unit-tests/builds/7/steps/** > run%20multiproduct%20tests/**logs/stdio<http://ci.apache.org/builders/bh-unit-tests/builds/7/steps/run%20multiproduct%20tests/logs/stdio> > ) > > On this platform, the multiproduct tests took almost 40 minutes to run so > it is probably a good idea to be attempting to optimise those. > > There are also two runs of bhdashboard tests that appear to not be running > correctly but I may need help in running them properly. In the longer term, > I would like to be removing the dutest dependency for these (I may have > already said this) but I realise this might take a bit of effort so that > can wait for a bit. > > Cheers, > Gary > Since this seems to be the most informative thread on the build slave, I thought it would be best to follow up here on the question raised earlier by Anze. http://markmail.org/message/zstxrgqcixwidiur Looking at the build config script some more, it looks like it will be fairly easy to add a notification to the dev list. I'd also like to try and fix the failure in the Trac unit test run that seems to be due to a missing Genshi import. How can I and other committers contribute to this script? What is the process for deploying the script to the build slave? If I checkout the script, make and test some changes locally and check it back in, will the modified configuration script get automatically picked up by the build slave?
