Yes Gav you are exactly right with this one... we have been building Gora locally and then locally building a tailored version of Nutch Trunk in order to get a successful build.
Looks like I'll be committing a downgrade of the two unresolved dependencies we highlighted to 0.1.1-incubating then wait until the next nightly build to see if we can get a successful build. I am awaiting approval from PMC chair to get an admin account setup so I can progress with setting up a nightly build for our 1.X-branch development as well. So one last quickie, we now have two Nutch trunk build jobs under builds.apache.org, I assume (once I or someone else gets admin rights) we can edit or delete one of these should we get it building successfully? Thank you for your help. Lewis On Thu, Aug 11, 2011 at 12:13 PM, Gavin McDonald <ga...@16degrees.com.au>wrote: > > > > -----Original Message----- > > From: lewis john mcgibbney [mailto:lewis.mcgibb...@gmail.com] > > Sent: Thursday, 11 August 2011 8:15 PM > > To: builds@apache.org > > Subject: Re: Nutch Trunk build failure for over 1 year > > > > Thank you both for getting back. > > > > In response to your comments Niklas, can you comment on where it would > > be preferred that we bind the builds to, e.g. Ubuntu or Solaris slaves? > It > > terms of preferrance from the dev@nutch team, I'm not sure we have a > > preferrence at the moment, and would just like to project to build, > however > > if you could shine some light on pro's con's of both configurations I > would be > > grateful. > > > > Yes I had no seen these errors due to unresolved dependencies and we can > > fix this with little effort, I think that these haven't been seen to due > to the > > fact that we hadn't seen a successful build in a looong time and no one > was > > looking into it. > > > > With regards to get a stable build back on track, are these the only > problems > > you envisage e.g. correcting both of the above? If this is the case then > I > > would like to think that this might be easier than I first thought, > however I am > > no holding my breath. > > I've been looking into this. > > First off, until we get a successful build I suggest we tie to one machine > only. > I've tied it to solaris1 currently. > > That got the build a bit further. > > Now it complains of two dependencies. > > [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: > [ivy:resolve] :: UNRESOLVED DEPENDENCIES :: > [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: > [ivy:resolve] :: org.apache.gora#gora-core;0.2-incubating: not > found > [ivy:resolve] :: org.apache.gora#gora-sql;0.2-incubating: not > found > [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: > [ivy:resolve] > [ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS > > (see > https://builds.apache.org/view/M-R/view/Nutch/job/Nutch-trunk/1574/console > ) > > Your (nutch) ivy.xml specifies these as: > > <dependency org="org.apache.gora" name="gora-sql" rev="0.2-incubating" > conf="*->compile"/> > <dependency org="org.apache.gora" name="gora-core" rev="0.2-incubating" > conf="*->compile"/> > > However, I can not find where these are released to. > > repository.apache.org I can see 0.1-incubating versions of those two > dependencies. No 0.2 anywhere, > so can someone enlighten me as to where 0.2 might be? (It isn't even > staged.) > > Looking at gora projects build.xml in trunk we have: > > <property name="version" value="0.2-incubating" /> > > So, if any of you nutch devs are in the 'works on my machine' type of > people, tell me did you build gora locally > to get the jars available for ivy or something else? > > 'works on my machine' - is exactly why we have build machines, so we can > test outside of the dev environment > where s/he may have local changes etc.. > > Let's sort out this dependency issue before going further. > > Thanks > > Gav... > > > > > > > Thanks again > > > > On Thu, Aug 11, 2011 at 11:06 AM, Niklas Gustavsson > > <nik...@protocol7.com>wrote: > > > > > On Thu, Aug 11, 2011 at 11:41 AM, lewis john mcgibbney > > > <lewis.mcgibb...@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: > > > https://builds.apache.org/view/M-R/view/Nutch/job/Nutch- > > trunk/1571/con > > > sole > > > > > > These you probably understand better than me. > > > > > > /niklas > > > > > > > > > > > -- > > *Lewis* > > -- *Lewis*
