[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485113#comment-15485113 ] Hudson commented on HBASE-15624: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1589 (See [https://builds.apache.org/job/HBase-Trunk_matrix/1589/]) HBASE-15624 Move master branch/hbase-2.0.0 to jdk-8 only (zhangduo: rev 105bfc7d7cd242fea384985a6a4e6ab7eced255f) * (edit) pom.xml * (edit) src/main/asciidoc/_chapters/configuration.adoc > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: stack >Assignee: Duo Zhang >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-15624-branch-1.patch, HBASE-15624-v1.patch, > HBASE-15624.patch, hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[
https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484152#comment-15484152
]
Duo Zhang commented on HBASE-15624:
---
{quote}
The doc change is in branch-1 only?
{quote}
No, it is on master. The patch for branch-1 here is only to prove that we still
check for java7 build on branches other than mater.
> Move master branch/hbase-2.0.0 to jdk-8 only
>
>
> Key: HBASE-15624
> URL: https://issues.apache.org/jira/browse/HBASE-15624
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-15624-branch-1.patch, HBASE-15624-v1.patch,
> HBASE-15624.patch, hbase-15624.patch
>
>
> Set build and pom target jvm version as jdk8. We chatted about it here:
> http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0.
> We need to work on YETUS-369 before we can finish up this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484120#comment-15484120 ] stack commented on HBASE-15624: --- Patch LGTM. The doc change is in branch-1 only? Do it on master branch on commit. > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: Duo Zhang >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-15624-branch-1.patch, HBASE-15624-v1.patch, > HBASE-15624.patch, hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483750#comment-15483750 ] Duo Zhang commented on HBASE-15624: --- [~busbey] Any other concerns? Thanks. > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: Duo Zhang >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-15624-branch-1.patch, HBASE-15624-v1.patch, > HBASE-15624.patch, hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[
https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483708#comment-15483708
]
Hadoop QA commented on HBASE-15624:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 15s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
40s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 16s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
5s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 36s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
46s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 20s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m 20s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
6s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 2s
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
24m 44s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green} 1m
9s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 36s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 94m 17s {color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
18s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 136m 22s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestScannerHeartbeatMessages |
| Timed out junit tests |
org.apache.hadoop.hbase.mapred.TestTableOutputFormatConnectionExhaust |
| | org.apache.hadoop.hbase.snapshot.TestMobSecureExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestMobRestoreFlushSnapshotFromClient |
| | org.apache.hadoop.hbase.security.access.TestTablePermissions |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:7bda515 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12827982/HBASE-15624-v1.patch |
| JIRA Issue | HBASE-15624 |
| Optional Tests | asflicense javac javadoc unit xml compile |
| uname | Linux 0355b4d3f6b3 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / c19d2ca |
| Default Java | 1.8.0_101 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/3501/artifact/patchprocess/patch-unit-root.txt
|
| unit test logs |
https://builds.apache.org/job/PreCommit-HBASE-Build/3501/artifact/patchprocess/patch-unit-root.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/3501/testReport/ |
| modules | C: . U: . |
| Console output |
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483351#comment-15483351 ] Duo Zhang commented on HBASE-15624: --- I think it is easy to add a line to the java table. I can prepare a new patch. But for the hadoop table, there is no agreement yet? Maybe it is better to file a new jira issue to discuss this? Thanks. > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: Duo Zhang >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-15624-branch-1.patch, HBASE-15624.patch, > hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[
https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483332#comment-15483332
]
Sean Busbey commented on HBASE-15624:
-
Could we include this bit:
{quote}
As a part of raising the visibility of this decision, could we start adding
HBase 2.0.0 to our prereq lists in the ref guide? With a disclaimer of
"tentative" or some such?
{quote}
We already list 1.3.x in the prerequisites section
([ref|http://hbase.apache.org/book.html#basic.prerequisites]), so there's
precedent for giving expected support details for versions that aren't out yet.
> Move master branch/hbase-2.0.0 to jdk-8 only
>
>
> Key: HBASE-15624
> URL: https://issues.apache.org/jira/browse/HBASE-15624
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-15624-branch-1.patch, HBASE-15624.patch,
> hbase-15624.patch
>
>
> Set build and pom target jvm version as jdk8. We chatted about it here:
> http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0.
> We need to work on YETUS-369 before we can finish up this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483079#comment-15483079 ] Duo Zhang commented on HBASE-15624: --- Perfect. Any concerns? [~busbey] [~stack] Thanks. > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: Duo Zhang >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-15624-branch-1.patch, HBASE-15624.patch, > hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[
https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483019#comment-15483019
]
Hadoop QA commented on HBASE-15624:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 22s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
58s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 13s
{color} | {color:green} branch-1 passed with JDK v1.8.0_101 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 15s
{color} | {color:green} branch-1 passed with JDK v1.7.0_111 {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
31s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 30s
{color} | {color:green} branch-1 passed with JDK v1.8.0_101 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 15s
{color} | {color:green} branch-1 passed with JDK v1.7.0_111 {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m 6s
{color} | {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 14s
{color} | {color:green} the patch passed with JDK v1.8.0_101 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 14s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 7s
{color} | {color:red} root in the patch failed with JDK v1.7.0_111. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 7s {color}
| {color:red} root in the patch failed with JDK v1.7.0_111. {color} |
| {color:red}-1{color} | {color:red} mvneclipse {color} | {color:red} 0m 7s
{color} | {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 1s
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 7s
{color} | {color:red} The patch causes 7 errors with Hadoop v2.4.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 13s
{color} | {color:red} The patch causes 7 errors with Hadoop v2.4.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 20s
{color} | {color:red} The patch causes 7 errors with Hadoop v2.5.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 26s
{color} | {color:red} The patch causes 7 errors with Hadoop v2.5.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 32s
{color} | {color:red} The patch causes 7 errors with Hadoop v2.5.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 38s
{color} | {color:red} The patch causes 7 errors with Hadoop v2.6.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 45s
{color} | {color:red} The patch causes 7 errors with Hadoop v2.6.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 51s
{color} | {color:red} The patch causes 7 errors with Hadoop v2.6.3. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 57s
{color} | {color:red} The patch causes 7 errors with Hadoop v2.7.1. {color} |
| {color:red}-1{color} | {color:red} hbaseprotoc {color} | {color:red} 0m 7s
{color} | {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 31s
{color} | {color:green} the patch passed with JDK v1.8.0_101 {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m 6s
{color} | {color:red} root in the patch failed with JDK v1.7.0_111. {color} |
| {color:red}-1{color} | {color:red} unit
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482888#comment-15482888 ] Duo Zhang commented on HBASE-15624: --- Seems fine? All javac related subsystems are executed once and the Default Java is '1.8.0_101'. The failed tests in unrelated I think since we do not change any java code? [~stack] [~busbey] Thanks. > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: Duo Zhang >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-15624.patch, hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[
https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482874#comment-15482874
]
Hadoop QA commented on HBASE-15624:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 15s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
52s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 15s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
6s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 37s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
44s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 20s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m 20s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
7s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 1s
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
24m 48s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green} 1m
9s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 37s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 93m 52s {color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
19s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 136m 15s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests |
org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestExportSnapshot |
| | org.apache.hadoop.hbase.TestMovedRegionsCleaner |
| | org.apache.hadoop.hbase.snapshot.TestMobRestoreFlushSnapshotFromClient |
| | org.apache.hadoop.hbase.mapred.TestTableSnapshotInputFormat |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:7bda515 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12827940/HBASE-15624.patch |
| JIRA Issue | HBASE-15624 |
| Optional Tests | asflicense javac javadoc unit xml compile |
| uname | Linux d182e688d421 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 7bda515 |
| Default Java | 1.8.0_101 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/3496/artifact/patchprocess/patch-unit-root.txt
|
| unit test logs |
https://builds.apache.org/job/PreCommit-HBASE-Build/3496/artifact/patchprocess/patch-unit-root.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/3496/testReport/ |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/3496/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> Move master branch/hbase-2.0.0 to jdk-8
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[
https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481538#comment-15481538
]
Duo Zhang commented on HBASE-15624:
---
This is the pre-commit build result with HBASE-16591 applied.
{noformat}
-1 overall
_ _ __
| ___|_ _(_) |_ _ _ __ ___| |
| |_ / _` | | | | | | '__/ _ \ |
| _| (_| | | | |_| | | | __/_|
|_| \__,_|_|_|\__,_|_| \___(_)
| Vote | Subsystem | Runtime | Comment
| 0 | reexec | 0m 6s | Docker mode activated.
| +1 | hbaseanti | 0m 0s | Patch does not have any anti-patterns.
| +1 |@author | 0m 0s | The patch does not contain any @author
| | || tags.
| -1 | test4tests | 0m 0s | The patch doesn't appear to include any
| | || new or modified tests. Please justify
| | || why no new tests are needed for this
| | || patch. Also please list what manual
| | || steps were performed to verify this
| | || patch.
| +1 | mvninstall | 52m 27s | master passed
| +1 |compile | 2m 42s| master passed
| +1 | mvneclipse | 3m 41s| master passed
| +1 |javadoc | 2m 53s| master passed
| +1 | mvninstall | 3m 10s| the patch passed
| +1 |compile | 2m 47s| the patch passed
| +1 | javac | 2m 47s| the patch passed
| +1 | mvneclipse | 1m 6s | the patch passed
| +1 | whitespace | 0m 0s | The patch has no whitespace issues.
| +1 |xml | 0m 1s | The patch has no ill-formed XML file.
| +1 |hadoopcheck | 37m 21s | Patch does not cause any errors with
| | || Hadoop 2.4.0 2.4.1 2.5.0 2.5.1 2.5.2
| | || 2.6.1 2.6.2 2.6.3 2.7.1.
| +1 |hbaseprotoc | 1m 28s| the patch passed
| +1 |javadoc | 1m 53s| the patch passed
| +1 | asflicense | 0m 50s| The patch does not generate ASF License
| | || warnings.
| | | 110m 30s |
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.1 Server=1.12.1 Image:yetus/hbase:7bda515 |
| Optional Tests | asflicense javac javadoc unit xml compile |
| uname | Linux 9a692c569b5e 3.13.0-96-generic #143-Ubuntu SMP Mon Aug 29
20:15:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /home/zhangduo/hbase/code/dev-support/hbase-personality.sh |
| git revision | master / 7bda515 |
| Default Java | 1.8.0_101 |
| modules | C: . U: . |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
Finished build.
{noformat}
Seems OK?
> Move master branch/hbase-2.0.0 to jdk-8 only
>
>
> Key: HBASE-15624
> URL: https://issues.apache.org/jira/browse/HBASE-15624
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: stack
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: hbase-15624.patch
>
>
> Set build and pom target jvm version as jdk8. We chatted about it here:
> http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0.
> We need to work on YETUS-369 before we can finish up this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15477186#comment-15477186 ] Sean Busbey commented on HBASE-15624: - Yep, that's the right approach. We'll also need docker files on the older branches with the right JVMs. > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15477040#comment-15477040 ] Duo Zhang commented on HBASE-15624: --- Great you are back! I have filed HBASE-16591 and I'm currently testing the dockerfile locally. Now it is running mvn install... Is it the right approach? Thanks. > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15477016#comment-15477016 ] Sean Busbey commented on HBASE-15624: - We just need someone to work through the precommit changes. > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15476128#comment-15476128 ] Duo Zhang commented on HBASE-15624: --- Let's do the same thing as hadoop on trunk? More and more issues are being blocked on this. > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411955#comment-15411955 ] Jurriaan Mous commented on HBASE-15624: --- Now that HBASE-15882 is fixed it should be possible to upgrade branch/hbase-2.0.0 to jdk8. YETUS-369 describes we need 2 docker files to do it. Can this be picked up so we can use the new JDK8 calls? (I need it for HBASE-15978) > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334472#comment-15334472 ] Sean Busbey commented on HBASE-15624: - there's a work around already described on YETUS-369. we could use it once HBASE-15882 is done and we can go back to Docker. > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334455#comment-15334455 ] Enis Soztutar commented on HBASE-15624: --- Any chance that we can get some love for YETUS-369? Should we look into workarounds in the mean time? > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: hbase-15624.patch > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[
https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333111#comment-15333111
]
Hadoop QA commented on HBASE-15624:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
10s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 26s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 25s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
4s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 26s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 20s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m 5s
{color} | {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 29s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m 29s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 6s
{color} | {color:red} root in the patch failed with JDK v1.7.0_79. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 6s {color}
| {color:red} root in the patch failed with JDK v1.7.0_79. {color} |
| {color:red}-1{color} | {color:red} mvneclipse {color} | {color:red} 0m 7s
{color} | {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 0s
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 6s
{color} | {color:red} Patch causes 7 errors with Hadoop v2.4.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 12s
{color} | {color:red} Patch causes 7 errors with Hadoop v2.4.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 18s
{color} | {color:red} Patch causes 7 errors with Hadoop v2.5.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 24s
{color} | {color:red} Patch causes 7 errors with Hadoop v2.5.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 30s
{color} | {color:red} Patch causes 7 errors with Hadoop v2.5.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 36s
{color} | {color:red} Patch causes 7 errors with Hadoop v2.6.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 41s
{color} | {color:red} Patch causes 7 errors with Hadoop v2.6.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 47s
{color} | {color:red} Patch causes 7 errors with Hadoop v2.6.3. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 53s
{color} | {color:red} Patch causes 7 errors with Hadoop v2.7.1. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 23s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m 6s
{color} | {color:red} root in the patch failed with JDK v1.7.0_79. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 0m 5s {color} |
{color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
11s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 20m 34s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12810987/hbase-15624.patch |
| JIRA
[jira] [Commented] (HBASE-15624) Move master branch/hbase-2.0.0 to jdk-8 only
[ https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235648#comment-15235648 ] Sean Busbey commented on HBASE-15624: - As a part of raising the visibility of this decision, could we start adding HBase 2.0.0 to our prereq lists in the ref guide? With a disclaimer of "tentative" or some such? Maybe also a note to user@ once that change is live on the website? > Move master branch/hbase-2.0.0 to jdk-8 only > > > Key: HBASE-15624 > URL: https://issues.apache.org/jira/browse/HBASE-15624 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > > Set build and pom target jvm version as jdk8. We chatted about it here: > http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0. > We need to work on YETUS-369 before we can finish up this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
