>From https://builds.apache.org/job/PreCommit-HBASE-Build/8283/consoleFull :
/usr/bin/java java version "1.6.0_20" ... /home/jenkins/tools/java/latest java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode) On Wed, Dec 25, 2013 at 9:02 PM, Andrew Purtell <[email protected]> wrote: > I should also mention the precommit builds all passed, which suggests to me > they are using JDK 7 also. > > > On Wed, Dec 25, 2013 at 9:00 PM, Andrew Purtell <[email protected]> > wrote: > > > HBASE-6104 introduced a feature developed and tested with JDK 7. > > Subsequent to review and commit, two builds on ASF Jenkins began failing, > > the 0.98 on Hadoop 1.1 build, and the trunk build. After chasing a red > > herring that looked like a test only failure for a bit it seems the > problem > > was deeper and manifested on JDK 6. I have reverted the change, > unscheduled > > the feature from 0.98, and may return to it some time in the future after > > the sting wears off. In the meantime, I have two suggestions: > > > > 1. We should set all of the primary builds like trunk and 0.98 on Hadoop > > 1.1 to use JDK 7, like the other builds. The inconsistent use of JDK/JRE > > version will be an occasional source of confusion. > > > > 2. We should explicitly set up jobs that use JDK/JRE 6 and name them as > > such. > > > > -- > > Best regards, > > > > - Andy > > > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > > (via Tom White) > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) >
