[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416700#comment-16416700
]
Hudson commented on HBASE-20272:
Results for branch HBASE-19064
[build #77 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19064/77//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16413036#comment-16413036
]
Hudson commented on HBASE-20272:
Results for branch master
[build #272 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/272/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/272//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/272//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/272//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412888#comment-16412888
]
Hudson commented on HBASE-20272:
Results for branch branch-2.0
[build #85 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/85/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/85//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/85//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/85//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412876#comment-16412876
]
Hudson commented on HBASE-20272:
Results for branch branch-2
[build #526 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/526/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/526//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/526//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/526//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412787#comment-16412787
]
Ted Yu commented on HBASE-20272:
bq. No reference to the issue that caused the problem
When I logged the JIRA, I was looking at why the TableExistsException happened
in the test.
I didn't look at git log closely to see which commit resulted in the test
failure.
Later I realized this was a regression. By the time I was about to link to
related issue, you already added the link (I needed to drive my kids to various
activities on Saturday).
Thanks for adding the link to the related issue, BTW.
bq. Why not just do an addendum on the original?
See above - I didn't pinpoint the related issue in the first place. I also
didn't want to cause confusion in case wrong issue was identified.
I will refer to the history more closely and use addendum on the original issue
in the future for test breakage.
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412764#comment-16412764
]
stack commented on HBASE-20272:
---
There are a few problems with this issue.
# No reference to the issue that caused the problem (HBASE-19504)
# Why not just do an addendum on the original?
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412504#comment-16412504
]
Chia-Ping Tsai commented on HBASE-20272:
+1
It is my mistake. Previous QA retried the failed test with single parameter so
it passed...
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412500#comment-16412500
]
Ted Yu commented on HBASE-20272:
[~chia7712]chia-ping:
Can you take a look as well ?
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412475#comment-16412475
]
Duo Zhang commented on HBASE-20272:
---
+1.
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412471#comment-16412471
]
Hadoop QA commented on HBASE-20272:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
37s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
1s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.7.0/precommit-patchnames for
instructions. {color} |
|| || || || {color:brown} Prechecks {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
51s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
2s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
20s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 6m
30s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
28s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
38s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
21s{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} shadedjars {color} | {color:green} 5m
11s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
20m 42s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
30s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}110m 10s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}161m 39s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.replication.TestReplicationDroppedTables |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-20272 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12916028/20272.v2.txt |
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 73efe65c8ab3 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9
14:43:09 UTC 2018 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 / 64ccd2b295 |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_162 |
| findbugs | v3.1.0-RC3 |
| unit |
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412429#comment-16412429
]
Hadoop QA commented on HBASE-20272:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
17s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
1s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.7.0/precommit-patchnames for
instructions. {color} |
|| || || || {color:brown} Prechecks {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
13s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
12s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
25s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
57s{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} shadedjars {color} | {color:green} 4m
14s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
18m 4s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}115m
52s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
17s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}157m 6s{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-20272 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12916020/20272.v1.txt |
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 84a8bbe736a1 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 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 / 64ccd2b295 |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_162 |
| findbugs | v3.1.0-RC3 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/12116/testReport/ |
| Max. process+thread count | 4426 (vs. ulimit of 1) |
| modules |
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412406#comment-16412406
]
Ted Yu commented on HBASE-20272:
Patch v2 removes the unnecessary table creation.
Test passes with v2 patch.
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412400#comment-16412400
]
Duo Zhang commented on HBASE-20272:
---
Does it still pass if you just remove the creation? Seems getTable.get() will
always use the TABLE_NAME...
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412356#comment-16412356
]
Ted Yu commented on HBASE-20272:
With the patch, the test finishes without error.
[~chia7712]:
Mind taking a look ?
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
