On Thu, Jan 13, 2011 at 1:14 AM, Giridharan Kesavan
<[email protected]>wrote:
>
> log=${ivyresolvelog} is set to quite for ivy-retrieve-common and
> ivy-resolve target in the top level build.xml file while this is not done at
> the contrib level ie src/contrib/build-contrib.xml
> Hence no verbose output for toplevel mapred project.
>
> I can pretty much confirm that this build is run against
> hadoop-common-0.23.0-20110111.025140-27.jar<
> https://repository.apache.org/content/groups/snapshots-group/org/apache/hadoop/hadoop-common/0.23.0-SNAPSHOT/hadoop-common-0.23.0-20110111.025140-27.jar>
> version of hadoop. ( I looked into the ivy cache).
> This is the latest available version of hadoop in the snapshot repository.
>
Then I think the Common build isn't publishing correctly.
The reason I ask is that the TestControlledMapReduceJob timeout should be
fixed by a recent change in Common. On my local box, if I do ant mvn-install
from common trunk, and then run this unit test using -Dresolvers=internal in
my mapred repo, it passes fine. If I drop resolvers=internal, and
clean-cache, it pulls the one from Apache and times out. It's pulling this:
https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-common/0.23.0-SNAPSHOT/hadoop-common-0.23.0-20110111.025140-27.jar
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
