Also, the tinderbox currently does make use of the existing unit tests in the server by running 'make check' after the build. I assume we could easily add these new unit tests to 'make check' and it will "just work"
... cjb, how do I add the rendercheck/x11perf/piglit/... runs to my tinderboxes? On Jan 2, 2012, at 12:41 PM, Chris Ball wrote: > Hi, > > On Mon, Jan 02 2012, Matt Dew wrote: >>> If I understand it correctly, tinderbox is a continuous integration >>> system (much like Jenkins) that compiles and executes unit tests. That >>> is, it should be no problem to execute the unit test executables built >>> with our framework/Google test. > > I agree, this is possible. You can run arbitrary code as a tinderbox > jhbuild "module", including running test binaries against the newly > built X server and recording their output. I've already got code that > runs rendercheck/x11perf/piglit/renderbench/cairotest/cairoperf and > reports the results, though this isn't running on most of the tinderbox > machines. > > I should add that our current tinderbox's use of jhautobuild is not so > much a conscious choice as a historical accident -- moving it over to > Jenkins would be a fine project if someone's interested in doing it. > > Thanks, > > - Chris. > -- > Chris Ball <c...@laptop.org> <http://printf.net/> > One Laptop Per Child > _______________________________________________ > xorg-devel@lists.x.org: X.Org development > Archives: http://lists.x.org/archives/xorg-devel > Info: http://lists.x.org/mailman/listinfo/xorg-devel > _______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
