www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niklas Gustavsson <nik...@protocol7.com>
Subject Re: Nutch Trunk build failure for over 1 year
Date Thu, 11 Aug 2011 10:06:04 GMT
On Thu, Aug 11, 2011 at 11:41 AM, lewis john mcgibbney
<lewis.mcgibbney@gmail.com> wrote:
> As a new committer on the Apache Nutch project, I'm on the war path to get
> our trunk build working as it was embarrassingly last seen working just over
> 1 year 1 month ago on 7-Jul-2010.
> If I point to the last log output showing the build failing I was wondering
> if anyone would be kind enough to point me in the right direction as to
> whether the build is failing due to problems on the dev@nutch side of things
> or whether it is the way that the Jenkins job in configured. From viewing
> the build specifics and log output shown here [1], I can't help but think
> that it is the latter of the two due to the following output:
> + /export/home/hudson/tools/ant/latest/bin/ant
> -Dversion=2011-08-11_04-01-22 -Dtest.junit.output.format=xml nightly
> /tmp/hudson2424857644284663135.sh: line 7:
> /export/home/hudson/tools/ant/latest/bin/ant: No such file or
> directory

There are some different types of problems with the build. First of
all, it's not bound to any particular set of slaves which means it
will sometimes build on ubuntu slaves. These have ant installed under
/home/hudson/tools/ant/latest/bin/ant. The /export directory is only
available on the solaria's slaves. So fix this or perhaps bind your
build to either ubuntu or solaris slaves.

Also, when the build happens to run on one of the solaris slaves, you
run into other issues:

These you probably understand better than me.


View raw message