: The most interesting bit is probably here... : : http://fucit.org/solr-jenkins-reports/failure-report.html
FYI: I realized this morning that the "Suite Runs" counts were being artificially inflated for suites that are frequently SKIPPED (either because they are @Nighly or @Slow and not run by all jenkins jobs). I've now fixed this, so at a glance the "suite level" failure rates are much higher today then they have been if you looked at it in the past. It means it's also now possible for a Suite failure rate to be greater then 100%, because sometimes it's reporting multiple suite level failures for a single run. Other follow up on some previous comments... : 1) there's some noise inthe '7days' data because I wasn't accounting for : the way jenkins reports some types of failure -- that will gradually clean : itself up ...some of these "Class: xml" failures are still visible in the report but should drop off over the next few days : 2) I think i've been been blocked by builds.apache.org, so at the moment : the data seems to just be from the sarowe & policeman jenkins failures. ...this is fixed. : 3) allthough the system is archiving the past 7 days worth of jenkins logs : for any jobs with failures, there is currently no easy way to download : the relevant log(s) from that failure report -- you currently have to ...this is also fixed. now if you click on any row in the test you'll get a pop up showing you a link to all the job-data dirs that recorded a failure on that report view. The most recent jobs are listed first. -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
