hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Kanter <rkan...@cloudera.com>
Subject Re: Set minimum version of Hadoop 3 to JDK 8
Date Wed, 22 Apr 2015 22:38:46 GMT
You're absolutely right Steve.  We should get the jobs under control.

At the very least, before we move to JDK 8 in Jenkins, we should get the
Java8 nightly builds working.  I didn't realize we had these, and I had
thought all compiling and most test issues with JDK8 were already fixed
based on what HADOOP-11090 looks like; but I guess there's more.

https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-common-trunk-Java8/
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-Hdfs-trunk-Java8/
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-Mapreduce-trunk-Java8/
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-Yarn-trunk-Java8/

I'll take a deeper look at these and file JIRAs as necessary later today.




On Wed, Apr 22, 2015 at 3:13 AM, Steve Loughran <stevel@hortonworks.com>
wrote:

>
> > On 21 Apr 2015, at 23:31, Andrew Wang <andrew.wang@cloudera.com> wrote:
> >
> > Hey Robert,
> >
> > As a first step, could we try switching all our precommit and nightly
> > builds over to use 1.8? This is a prerequisite for HADOOP-11858, and safe
> > to do in any case since it'll still target 1.7.
>
> +1
>
> we have jenkin builds running on Java 8 -its just they have enough
> longstanding and intermittent test failures that they get ignored
>
> I've been trying to keep hadoop-common somewhat under control, but
>
> -YARN is failing due to to hard coded ports in tests - this needs to be
> fixed urgently: YARN-3528
> -HDFS build process itself is failing with some config problem checkstyle
>
>
> >
> > I'll note that HADOOP-10530 details the pain Steve went through switching
> > us to JDK7. Might be some lessons learned about how to do this transition
> > more smoothly.
> >
>
>
> The key thing is to have Jenkins happy before trying to change anything.
> And make sure that "happy" means that jenkins really is building and
> testing against the version of Java that you think it is. I spent about 15
> minutes/hour of my weekend kicking off builds and tuning them.  -I
> volunteered Colin Patrick McCabe to to that bit of the switch, though of
> course he doesn't have to accept that opportunuty (
> https://issues.apache.org/jira/browse/HADOOP-10530?focusedCommentId=14239250&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14239250
>
> Someone needs to take ownership of the "Jenkins builds are broken" problem
> -ideally someone in each subproject. That's a prerequisite to any major
> changes in the build process, but should also be best practice anyway. Ask
> your QE teams "would you like the ASF projects to care whether their
> jenkins test runs succeed" and see what they say.
>
> as a reminder, all the jenkins builds are here
> https://builds.apache.org/view/H-L/view/Hadoop/
>
> please look at them and try to fix them —without even waiting for a switch
> to Java 8

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message