[jira] [Commented] (HBASE-19119) hbase-http shouldn't have a native profile
[ https://issues.apache.org/jira/browse/HBASE-19119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225793#comment-16225793 ] Hudson commented on HBASE-19119: FAILURE: Integrated in Jenkins build HBase-2.0 #774 (See [https://builds.apache.org/job/HBase-2.0/774/]) HBASE-19119 hbase-http shouldn't have native profile (mdrob: rev 3de44f918b39912dc3d72948e724aed052419717) * (edit) hbase-http/pom.xml > hbase-http shouldn't have a native profile > -- > > Key: HBASE-19119 > URL: https://issues.apache.org/jira/browse/HBASE-19119 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0-alpha-4 >Reporter: Mike Drob >Assignee: Mike Drob >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19119.patch > > > When splitting out the hbase-http module in HBASE-19053 we accidentally > included a native profile that will fail when invoked. I think we can just > nix that section since the native code is still in hbase-server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19119) hbase-http shouldn't have a native profile
[ https://issues.apache.org/jira/browse/HBASE-19119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225777#comment-16225777 ] Hudson commented on HBASE-19119: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3974 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3974/]) HBASE-19119 hbase-http shouldn't have native profile (mdrob: rev a79b66b32b4e3eb98fb1c03cb545b8edeab26647) * (edit) hbase-http/pom.xml > hbase-http shouldn't have a native profile > -- > > Key: HBASE-19119 > URL: https://issues.apache.org/jira/browse/HBASE-19119 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0-alpha-4 >Reporter: Mike Drob >Assignee: Mike Drob >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19119.patch > > > When splitting out the hbase-http module in HBASE-19053 we accidentally > included a native profile that will fail when invoked. I think we can just > nix that section since the native code is still in hbase-server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19119) hbase-http shouldn't have a native profile
[ https://issues.apache.org/jira/browse/HBASE-19119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225415#comment-16225415 ] Hadoop QA commented on HBASE-19119: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 4m 15s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {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:brown} master Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m 18s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 26s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 15m 14s{color} | {color:green} branch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 22s{color} | {color:green} master passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m 40s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 31s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 31s{color} | {color:green} the patch passed {color} | | {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 0s{color} | {color:red} The patch has 473 line(s) that end in whitespace. Use git apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply {color} | | {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 22s{color} | {color:red} The patch 384 line(s) with tabs. {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} shadedjars {color} | {color:green} 6m 37s{color} | {color:green} patch has no errors when building our shaded downstream artifacts. {color} | | {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 73m 27s{color} | {color:green} Patch does not cause any errors with Hadoop 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 0s{color} | {color:green} hbase-http in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 12s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black}103m 56s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 | | JIRA Issue | HBASE-19119 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12894767/HBASE-19119.patch | | Optional Tests | asflicense javac javadoc unit shadedjars hadoopcheck xml compile | | uname | Linux dc4eccf21359 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11 12:48:20 UTC 2017 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 / e0a530e714 | | Default Java | 1.8.0_141 | | whitespace | https://builds.apache.org/job/PreCommit-HBASE-Build/9518/artifact/patchprocess/whitespace-eol.txt | | whitespace | https://builds.apache.org/job/PreCommit-HBASE-Build/9518/artifact/patchprocess/whitespace-tabs.txt | | Test Results | https://builds.apache.org/job/PreCommit-HBASE-Build/9518/testReport/ | | modules | C: hbase-http U: hbase-http | | Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/9518/console | | Powered by | Apache Yetus 0.5.0 http://yetus.apache.org | This message was automatically generated. > hbase-http shouldn't have a native profile > -- > > Key: HBASE-19119 > URL:
[jira] [Commented] (HBASE-19119) hbase-http shouldn't have a native profile
[ https://issues.apache.org/jira/browse/HBASE-19119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225285#comment-16225285 ] Mike Drob commented on HBASE-19119: --- pushed, committed ahead of QA because that doesn't have tests for native profile anyway. > hbase-http shouldn't have a native profile > -- > > Key: HBASE-19119 > URL: https://issues.apache.org/jira/browse/HBASE-19119 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0-alpha-4 >Reporter: Mike Drob >Assignee: Mike Drob >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19119.patch > > > When splitting out the hbase-http module in HBASE-19053 we accidentally > included a native profile that will fail when invoked. I think we can just > nix that section since the native code is still in hbase-server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19119) hbase-http shouldn't have a native profile
[ https://issues.apache.org/jira/browse/HBASE-19119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225270#comment-16225270 ] Sean Busbey commented on HBASE-19119: - +1 > hbase-http shouldn't have a native profile > -- > > Key: HBASE-19119 > URL: https://issues.apache.org/jira/browse/HBASE-19119 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0-alpha-4 >Reporter: Mike Drob >Assignee: Mike Drob >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19119.patch > > > When splitting out the hbase-http module in HBASE-19053 we accidentally > included a native profile that will fail when invoked. I think we can just > nix that section since the native code is still in hbase-server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19119) hbase-http shouldn't have a native profile
[ https://issues.apache.org/jira/browse/HBASE-19119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225181#comment-16225181 ] stack commented on HBASE-19119: --- +1 > hbase-http shouldn't have a native profile > -- > > Key: HBASE-19119 > URL: https://issues.apache.org/jira/browse/HBASE-19119 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0-alpha-4 >Reporter: Mike Drob >Assignee: Mike Drob >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19119.patch > > > When splitting out the hbase-http module in HBASE-19053 we accidentally > included a native profile that will fail when invoked. I think we can just > nix that section since the native code is still in hbase-server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)