On Fri, 2013-02-15 at 11:54 +0100, Martin Pitt wrote: > Martin Pitt [2013-02-12 7:43 +0100]: > > https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild%20Gnome/ > > > > Right now there are 151 successes (blue), 5 modules fail to build > > (red), and 4 modules build but fail in "make check" (yellow). It's > > been like that for a week or two now, so I'd say we are doing > > reasonably well for now. > > You may have seen the sudden large increase of test failures on Feb > 13, we are back at ~ 40 "make check failures". It turns out that this > isn't due to a regression in our test environment after all, as I > initially suspected, but because of a bug fix. Until Feb 13, "make > check" wasn't run on a build which previously succeeded already, due > to an accidentally dropped "--force" jhbuild option. It has been put > back. > > So the current failures have been there all along. Sorry for the > confusion!
Speaking of test failures - is it possible to get more details? All I can seem to turn up for the "folks" module test failures are: "make check failed for folks Check log file for details" But I can't seem to find the corresponding log from here: https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild% 20Gnome/job/jhbuild-amd64-folks/lastSuccessfulBuild/testReport/junit/folks/test/make_check/ Also, most modules say "1 of 1 tests {failed, succeeded}". I guess this is a side effect of "make check" being somewhat monolithic. Is there any way modules can increase the granularity reported for tools like Jenkins? Thanks, -Travis
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
