RE: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193
From: Robert Muir [mailto:[hidden email]]
Sent: Wednesday, September 26, 2012 6:22 AM
To: [hidden email] Subject: Re: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193
Can we improve the way the smoketester works here?
I've been running lucene's tests in loops for a really long time now
trying to provoke any test fail, but now i finally provoked one and we
never will know what it is.
Instead of 'see /path/to/log' when something fails, can we just cat
/path/to/log to stdout when something fails?