Julien, this _SUCCESS file is not 0.21 specific but originates from 0.20
series. At the time the first issues came Nutch was still at 0.20, that was as
early as june 2011 NUTCH-1029.
That, however, doesn't answer why you never had failing tests.
On Thursday 05 January 2012 12:14:52 Julien
This issue? https://issues.apache.org/jira/browse/MAPREDUCE-947
It indeed says 0.21 but it's written on 20.203 deployments as well. Now i know
why i saw the tests failing all the time because my system has 0.20.203 but
Nutch had 0.20 just before i upgraded Nutch itself to 0.20.205.0.
I'm
I've quickly spun a Jenkins build and all looks good.
Thanks
Lewis
On Thu, Jan 5, 2012 at 11:42 AM, Markus Jelsma
markus.jel...@openindex.io wrote:
This issue? https://issues.apache.org/jira/browse/MAPREDUCE-947
It indeed says 0.21 but it's written on 20.203 deployments as well. Now i know
guys,
any idea as to why this is not compiling anymore?
J.
On 4 January 2012 04:20, Apache Jenkins Server jenk...@builds.apache.orgwrote:
See https://builds.apache.org/job/Nutch-trunk/1714/
--
[...truncated 2386 lines...]
resolve-default:
No, but iirc it started to show up sometime after lewis was working on
removing logutil. I don't how they might have anything to do with eachother
though.
Also, noone has been working in the urlfilter package for a long time.
On Wednesday 04 January 2012 10:52:08 Julien Nioche wrote:
guys,
The problem is not with the urlfilter package as such but with the fact
that the junit jar is removed from the lib dir before compiling the tests.
This is due to the fact that the job task is called prior to executing the
test and I assume that it deletes whatever specific to the test config had
Note : the latest stable is 1215090 i.e. things started to get bad when
moving to hadoop 0.22 (rev 1220786).
On 4 January 2012 16:45, Julien Nioche lists.digitalpeb...@gmail.comwrote:
The problem is not with the urlfilter package as such but with the fact
that the junit jar is removed from the
Yes, that is correct, with 0.22 things happened to go strange. But the current
trunk is not upgraded to 0.22 but upgraded to 0.20.205.0. I cannot seem
reproduce any compilation error, even when cleaning my build directory, and
only the known tests fail (crawl merger and outlink extractor).
Any
Yes, that is correct, with 0.22 things happened to go strange. But the
current
trunk is not upgraded to 0.22 but upgraded to 0.20.205.0. I cannot seem
reproduce any compilation error, even when cleaning my build directory, and
only the known tests fail (crawl merger and outlink extractor).
Uh, it's actually both segment and crawldb merger tests that fail on a clean
build. The outlink extractor fails in one of my tests builds. I can't remember
them working properly in a clean build at all.
Did you see them passing the last time you ran the tests? If so, then there's
something
Yes you are right, i meant both merger tests fail in a clean and regular
build.
Hi Guys,
Looking at my two commits e.g. NUTCH-1217 1138, I see no possible problem
with 1217 as this was merely content based as oppose to code based.
Therefore if we agree, then I am happy to revert 1138 for
As far as I was aware all tests were passing swimmingly until recently
(9 days ago). We had a stable CI build for a good few weeks at least.
Until tonight the CI build only archived the last 10 builds, however
this has now been changed to archive the last 50 builds.
Can we agree on some actions
See https://builds.apache.org/job/Nutch-trunk/1714/
--
[...truncated 2386 lines...]
resolve-default:
[ivy:resolve] :: loading settings :: file =
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/Nutch-trunk/trunk/ivy/ivysettings.xml
compile:
13 matches
Mail list logo
