: great and very helpful! Does it only contain Solr or are there also Lucene tests reported?

That was just a dumb choice on my part when creating the fucit.org URL
since the vast majority of the jenkins failures are in Solr tests.

It's really every test failure reported from any build of any jenkins jobs
in one of the feeds it's tracking...

https://github.com/hossman/jenkins-reports/blob/master/venus.ini#L66

(BTW: If you could setup a "jenkins view" for only the "Lucene/Solr" jobs
on your jenkins server -- similar to what we have on builds.apache and
sarowe's jenkins -- that would help reduce the noise in the report if/when
there are any test failures in other non-lucene jenkins jobs you have
running)
If, for example, you type "org.apache.lucene" in the text box in the class
column, it will filter down to only show you test failures from lucene
package tests -- like for example: in the past 24 hours,
oal.search.TestSearcherManager has had suite level failures in 10% of the
jenkins builds in which it run...

   http://fucit.org/solr-jenkins-reports/failure-report.html

: > -----Original Message-----
: > From: Chris Hostetter [mailto:[EMAIL PROTECTED]]
: > Sent: Thursday, February 22, 2018 1:56 AM
: > To: [EMAIL PROTECTED]
: > Subject: Re: Test failures are out of control......
: >
: >
: > : * Hoss has worked on aggregating all test failures from the 3 Jenkins
: > : systems (ASF, Policeman, and Steve's), downloading the test results & logs,
: > : and running some reports/stats on failures. He should be ready to share
: > : this more publicly soon.
: >
: > I think Steve's linked to some of this before from jira comments, but it
: > was only recently I realized i've never explicitly said to the list "Hey
: > folks, here's a thing i've been working on" ...
: >
: >   http://fucit.org/solr-jenkins-reports/
: >   https://github.com/hossman/jenkins-reports/
: >
: > The most interesting bit is probably here...
: >
: >   http://fucit.org/solr-jenkins-reports/failure-report.html
: >
: > ...but there are currently a few caveats:
: >
: > 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
: >
: > 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.
: >
: > 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
: > download a CSV file like this one to corrolate the test failures to the
: > jenkins job, and then go look for that job in the job-data dirs...
: >
: >   http://fucit.org/solr-jenkins-reports/reports/7days-method-failures.csv
: >   http://fucit.org/solr-jenkins-reports/job-data/
: >
: > (My hope is to make #3 trivial from failure-report.html -- so you can say
: > "hey weird, this test has failed X times, let's go download those logs."
: > right from a single screen in your browser)
: >
: >
: >
: >
: > -Hoss
: > http://www.lucidworks.com/
: >
: > ---------------------------------------------------------------------
: > To unsubscribe, e-mail: [EMAIL PROTECTED]
: > For additional commands, e-mail: [EMAIL PROTECTED]
:
:
: ---------------------------------------------------------------------
: To unsubscribe, e-mail: [EMAIL PROTECTED]
: For additional commands, e-mail: [EMAIL PROTECTED]
:
:

-Hoss
http://www.lucidworks.com/

---------------------------------------------------------------------
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB