I think the RAT build has been broken for a while: http://ci.apache.org/builders/lucy-trunk-rat
At this point I'm not certain what could possibly be wrong, other than it's probably looking for the wrong file name. As discussed on IRC, I'll go ahead and take the liberty and forward this [email protected] and [email protected] for assistance. Thanks, Logan On Thu, Jan 12, 2012 at 3:52 PM, Marvin Humphrey <[email protected]> wrote: > On Wed, Jan 11, 2012 at 04:08:17PM -0600, Peter Karman wrote: >> Marvin Humphrey wrote on 1/11/12 3:27 PM: >> >> > Please also commit those license header changes to trunk. It will be >> > great to >> > see <http://ci.apache.org/projects/lucy/rat-output.html> passing once >> > again. >> > >> >> I did last night, in >> http://svn.apache.org/viewvc?view=revision&revision=1229867 >> >> /me is wondering why RAT is not seeing that... > > It may be that the RAT buildbot is broken right now. > > Here's the current RAT build result: > > http://ci.apache.org/builders/lucy-trunk-rat/builds/120 > > I got to that page by following links from these pages: > > http://ci.apache.org/ > http://ci.apache.org/buildbot.html > http://ci.apache.org/builders > http://ci.apache.org/builders/lucy-trunk-rat > > It seems suspicious that this is the failing step: > > 3. upload uploading rat-output.xml ( 0 secs ) > > Here's the content of stderr for that step: > > Cannot open file > '/home/buildslave2/slave2/lucy-trunk-rat/build/../rat-output.xml' for > upload > > Logan pointed me at our buildbot config: > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/lucy.conf > > This appears to be the step that's failing: > > # Above performs RAT tests on entire lucy build directories, output to txt > file. > # Now we will publish that report to > ci.apache.org/projects/lucy/rat-output.xml > # assuming that the report step itself was successful. > > f_lucy_1.addStep(rat_report_upload(slavesrc="../rat-output.xml", > masterdest="/tmp/lucy/rat-output.xml", > haltOnFailure=True, > )) > > Dunno why it's b0rken, or how to fix it myself. > > I think the next step is to escalate to the [email protected] list. > > http://mail-archives.apache.org/mod_mbox/www-builds/ > > Marvin Humphrey >
