You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Ted Yu <yu...@gmail.com> on 2012/05/18 06:53:10 UTC

test failure after upgrading to hadoop 1.0.3 Was: ClassNotFoundException: org.apache.commons.io.FileUtils

See the following.

---------- Forwarded message ----------
From: Ted Yu <yu...@gmail.com>
Date: Thu, May 17, 2012 at 9:37 PM
Subject: Re: ClassNotFoundException: org.apache.commons.io.FileUtils
To: mapreduce-dev@hadoop.apache.org


I changed hadoop version to 1.0.2 and the test passed.

I would tend to say 1.0.3 had a regression in this regard.

Cheers


On Thu, May 17, 2012 at 8:11 PM, Ted Yu <yu...@gmail.com> wrote:

> Correction to my first email:
> I refreshed my HBase 0.92 workspace and I could see the same test failure.
>
> Under ~/.m2/repository/org/apache/commons/commons-io, I still see 1.3.2
>
> I ran 'mvn dependency:tree' under 0.92 and don't see commons-io in the
> output.
>
> Do we need to include commons-io explicitly in our pom.xml ?
>
> For Todd's question:
>
> LM-SJN-00713032:205-hadoop zhihyu$ svn info
> Path: .
> URL: https://svn.apache.org/repos/asf/hadoop/common/branches/branch-1
> Repository Root: https://svn.apache.org/repos/asf
> Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
> Revision: 1339961
> Node Kind: directory
> Schedule: normal
> Last Changed Author: mattf
> Last Changed Rev: 1339945
> Last Changed Date: 2012-05-17 18:25:57 -0700 (Thu, 17 May 2012)
>
> The line I referenced in my first email came from ivy/libraries.properties
>
>
> On Thu, May 17, 2012 at 8:06 PM, Todd Lipcon <to...@cloudera.com> wrote:
>
>> I believe we upgraded to commons-io 3.0 in 1.0.3. Did you check the 1.0.3
>> pom?
>>
>> -Todd
>>
>> On Thu, May 17, 2012 at 8:01 PM, Ted Yu <yu...@gmail.com> wrote:
>> > Hi,
>> > HBase 0.92 upgraded hadoop to 1.0.3 today.
>> > We started seeing some test failures which we didn't see before. e.g.:
>> >
>> https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/410/testReport/org.apache.hadoop.hbase.mapred/TestTableMapReduce/testMultiRegionTable/
>> > Here is the interesting part:
>> >
>> > Caused by: java.lang.ClassNotFoundException:
>> org.apache.commons.io.FileUtils
>> >        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>> >        at java.security.AccessController.doPrivileged(Native Method)
>> >        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>> >        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>> >        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>> >        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>> >        ... 15 more
>> >
>> > In hadoop 1.0, I see:
>> > commons-io.version=2.1
>> >
>> > HBase doesn't specify commons-io version.
>> >
>> > When I run the same test on MacBook, I don't see the test fail.
>> >
>> > commons-io in local mvn repo is 1.3.2
>> >
>> > If someone can give me hint on why the unit test failed, that would be
>> > great.
>>
>>
>>
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
>>
>
>

Re: test failure after upgrading to hadoop 1.0.3 Was: ClassNotFoundException: org.apache.commons.io.FileUtils

Posted by Luke Lu <ll...@apache.org>.
You're right, Ted. This is caused by HADOOP-6963 forgetting to update
the hadoop pom. Please file a bug.

Thanks.

__Luke

On Thu, May 17, 2012 at 9:53 PM, Ted Yu <yu...@gmail.com> wrote:
> See the following.
>
> ---------- Forwarded message ----------
> From: Ted Yu <yu...@gmail.com>
> Date: Thu, May 17, 2012 at 9:37 PM
> Subject: Re: ClassNotFoundException: org.apache.commons.io.FileUtils
> To: mapreduce-dev@hadoop.apache.org
>
>
> I changed hadoop version to 1.0.2 and the test passed.
>
> I would tend to say 1.0.3 had a regression in this regard.
>
> Cheers
>
>
> On Thu, May 17, 2012 at 8:11 PM, Ted Yu <yu...@gmail.com> wrote:
>
>> Correction to my first email:
>> I refreshed my HBase 0.92 workspace and I could see the same test failure.
>>
>> Under ~/.m2/repository/org/apache/commons/commons-io, I still see 1.3.2
>>
>> I ran 'mvn dependency:tree' under 0.92 and don't see commons-io in the
>> output.
>>
>> Do we need to include commons-io explicitly in our pom.xml ?
>>
>> For Todd's question:
>>
>> LM-SJN-00713032:205-hadoop zhihyu$ svn info
>> Path: .
>> URL: https://svn.apache.org/repos/asf/hadoop/common/branches/branch-1
>> Repository Root: https://svn.apache.org/repos/asf
>> Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
>> Revision: 1339961
>> Node Kind: directory
>> Schedule: normal
>> Last Changed Author: mattf
>> Last Changed Rev: 1339945
>> Last Changed Date: 2012-05-17 18:25:57 -0700 (Thu, 17 May 2012)
>>
>> The line I referenced in my first email came from ivy/libraries.properties
>>
>>
>> On Thu, May 17, 2012 at 8:06 PM, Todd Lipcon <to...@cloudera.com> wrote:
>>
>>> I believe we upgraded to commons-io 3.0 in 1.0.3. Did you check the 1.0.3
>>> pom?
>>>
>>> -Todd
>>>
>>> On Thu, May 17, 2012 at 8:01 PM, Ted Yu <yu...@gmail.com> wrote:
>>> > Hi,
>>> > HBase 0.92 upgraded hadoop to 1.0.3 today.
>>> > We started seeing some test failures which we didn't see before. e.g.:
>>> >
>>> https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/410/testReport/org.apache.hadoop.hbase.mapred/TestTableMapReduce/testMultiRegionTable/
>>> > Here is the interesting part:
>>> >
>>> > Caused by: java.lang.ClassNotFoundException:
>>> org.apache.commons.io.FileUtils
>>> >        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>>> >        at java.security.AccessController.doPrivileged(Native Method)
>>> >        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>>> >        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>>> >        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>>> >        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>> >        ... 15 more
>>> >
>>> > In hadoop 1.0, I see:
>>> > commons-io.version=2.1
>>> >
>>> > HBase doesn't specify commons-io version.
>>> >
>>> > When I run the same test on MacBook, I don't see the test fail.
>>> >
>>> > commons-io in local mvn repo is 1.3.2
>>> >
>>> > If someone can give me hint on why the unit test failed, that would be
>>> > great.
>>>
>>>
>>>
>>> --
>>> Todd Lipcon
>>> Software Engineer, Cloudera
>>>
>>
>>