Hadoop-Mapreduce-trunk-Java8 - Build # 124 - Still Failing

2015-03-06 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/124/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10597 lines...] Results : Failed tests: Te

Hadoop-Mapreduce-trunk - Build # 2074 - Still Failing

2015-03-06 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2074/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 31201 lines...] Tests run: 3, Failures: 0, Errors: 0

Re: Looking to a Hadoop 3 release

2015-03-06 Thread Allen Wittenauer
Right, but that doesn't really answer the question…. On Mar 5, 2015, at 10:23 PM, Alejandro Abdelnur wrote: > If classloader isolation is in place, then dependency versions can freely > be upgraded as won't pollute apps space (things get trickier if there is an > ON/OFF switch). > > On Thu, Ma

Re: Looking to a Hadoop 3 release

2015-03-06 Thread Andrew Wang
Since these dependency bumps are very disruptive to downstreams, I want to predicate upgrading our deps on having classpath isolation on. I think that's what Tucu was getting at. Best, Andrew On Fri, Mar 6, 2015 at 8:01 AM, Allen Wittenauer wrote: > > Right, but that doesn't really answer the q

Re: Looking to a Hadoop 3 release

2015-03-06 Thread Vinod Kumar Vavilapalli
Yes, these are the kind of enhancements that need to be proposed and discussed for inclusion! Thanks, +Vinod On Mar 5, 2015, at 3:21 PM, Siddharth Seth wrote: > Some features that come to mind immediately would be > 1) enhancements to the RPC mechanics - specifically support for AsynRPC / > t

Re: Looking to a Hadoop 3 release

2015-03-06 Thread Vinod Kumar Vavilapalli
I'd encourage everyone to post their wish list on the Roadmap wiki that *warrants* making incompatible changes forcing us to go 3.x. +1 to Jason's comments on general. We can keep rolling alphas that downstream can pick up, but I'd also like us to clarify the exit criterion for a GA release of

Re: Looking to a Hadoop 3 release

2015-03-06 Thread Andrew Wang
Hey Vinod, I'm roughly okay with that plan. One question though, why gate JDK8 on a 2.8 and 2.9? Based on the status of HADOOP-11090, it sounds like branch-2 already runs okay on JDK8. Our past experience moving from JDK6 to JDK7 was also very smooth except for JUnit ordering. As an additional da

Re: Looking to a Hadoop 3 release

2015-03-06 Thread Chris Douglas
On Fri, Mar 6, 2015 at 4:32 PM, Vinod Kumar Vavilapalli wrote: > I'd encourage everyone to post their wish list on the Roadmap wiki that > *warrants* making incompatible changes forcing us to go 3.x. This is a useful exercise, but not a prerequisite to releasing 3.0.0 as an alpha off of trunk, r