This looks good to me this morning. Patrick, thank you for following up. --Chris Nauroth
On 3/19/16, 6:43 PM, "Patrick Hunt" <[email protected]> wrote: >Gavin (infra) fixed this. We should be back in business. > >Patrick > >On Sat, Mar 19, 2016 at 4:33 PM, Patrick Hunt <[email protected]> wrote: >> ps it doesn't look like anyone has changed that job config in quite >>some time: >> >> >>https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER >>-Build/jobConfigHistory/ >> >> Patrick >> >> >> On Sat, Mar 19, 2016 at 4:29 PM, Patrick Hunt <[email protected]> wrote: >>> Hi Chris. I filed this issue earlier this morning based on failures in >>> some of our other jobs: >>> >>> https://issues.apache.org/jira/browse/INFRA-11488 >>> >>> It would help if you could comment on this jira, I don't believe what >>> I saw is the same but it sounds similar. >>> >>> Patrick >>> >>> On Sat, Mar 19, 2016 at 2:37 PM, Chris Nauroth >>><[email protected]> wrote: >>>> Is anyone aware of recent changes in our Jenkins jobs that would have >>>>started using JDK 8 instead of JDK 7 for pre-commit? We're not ready >>>>for this, because there are some different rules about JavaDocs in JDK >>>>8, and the ZooKeeper codebase currently triggers warnings due to >>>>violations of those new rules. >>>> >>>> Here are examples of pre-commit jobs than ran with JDK 8: >>>> >>>> >>>>https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3108/consoleTex >>>>t >>>> >>>> >>>>https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3109/consoleTex >>>>t >>>> >>>> Those 2 builds ran on different Jenkins hosts, so it's not specific >>>>to a particular host. >>>> >>>> The strange thing is that the job appears to be configured to use JDK >>>>7, and the file path in the output appears that it should be JDK 7, >>>>but it still ends up using JDK 8. >>>> >>>> /home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7/bin/java >>>> java version "1.8.0_66" >>>> Java(TM) SE Runtime Environment (build 1.8.0_66-b17) >>>> Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode) >>>> >>>> If no one is aware of changes in our jobs that would have caused >>>>this, then perhaps we'll need to ask infrastructure for help. Maybe >>>>something strange happened, like an accidental installation of JDK 8 >>>>at the JDK 7 path. >>>> >>>> --Chris Nauroth >
