[
https://issues.apache.org/jira/browse/HBASE-19204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258199#comment-16258199
]
stack commented on HBASE-19204:
-------------------------------
bq. Do you still look for the cryptic JVM version?
Good stuff [~chia7712] You've seen HDFS-12711? It is about some (or various)
items in hdfs that are blowing up tests.
As you can tell I put the investigation aside. Seems like its back again with a
vengeance. But how comes when I build locally w/ jdk8_73 I see timeouts (have
not checked if they are same as the type you identify above ... I see similar
looking timeouts on branch-2 builds...
https://builds.apache.org/job/HBase%20Nightly/job/branch-2/119/artifact/output-jdk8/patch-unit-root.txt)?
The old style 1.2 build is broke.
https://builds.apache.org/view/H-L/view/HBase/job/HBase-1.2-JDK7/ It is using
the 'latest' jdk7 available. The nightly jdk7 1.2 build is using 1.7.0_151
(one of the hangling jdk7s going by your finding above) and Apache Maven 3.0.5.
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java The last good nightly failed the
hbase-server second part tests with timeouts...
https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/131/artifact/output-jdk7/patch-unit-root.txt
Possible to compile w/ 1.7 but run w/ 1.8 [~busbey]? Our yetus probably doesn't
allow this?
> branch-1.2 times out and is taking 6-7 hours to complete
> --------------------------------------------------------
>
> Key: HBASE-19204
> URL: https://issues.apache.org/jira/browse/HBASE-19204
> Project: HBase
> Issue Type: Umbrella
> Components: test
> Reporter: stack
>
> Sean has been looking at tooling and infra. This Umbrellas is about looking
> at actual tests. For example, running locally on dedicated machine I picked a
> random test, TestPerColumnFamilyFlush. In my test run, it wrote 16M lines. It
> seems to be having zk issues but it is catching interrupts and ignoring them
> ([~carp84] fixed this in later versions over in HBASE-18441).
> Let me try and do some fixup under this umbrella so we can get a 1.2.7 out
> the door.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
