[
https://issues.apache.org/jira/browse/HBASE-26244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408302#comment-17408302
]
Hudson commented on HBASE-26244:
--------------------------------
Results for branch branch-2.3
[build #284 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/284/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/284/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/284/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/284/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/284/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Avoid trim the error stack trace when running UT with maven
> -----------------------------------------------------------
>
> Key: HBASE-26244
> URL: https://issues.apache.org/jira/browse/HBASE-26244
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha-1, 2.4.5
> Reporter: chenglei
> Assignee: chenglei
> Priority: Major
> Fix For: 1.4.14, 2.5.0, 3.0.0-alpha-2, 1.7.2, 2.4.6, 2.3.7
>
>
> When running HBase unit test with maven, if there is failed test，I always
> find that the error stack trace was trimmed, which make it is hard to locate
> the root cause.
> Just see the following stack trace as an example:
> {code:java}
> [INFO] Running org.apache.hadoop.hbase.regionserver.TestHStore
> [ERROR] Tests run: 32, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 34.516 s <<< FAILURE! - in org.apache.hadoop.hbase.regionserver.TestHStore
> [ERROR]
> org.apache.hadoop.hbase.regionserver.TestHStore.testCompactingMemStoreWriteLargeCellAndSmallCellConcurrently
> Time elapsed: 0.44 s <<< FAILURE!
> java.lang.AssertionError
> at
> org.apache.hadoop.hbase.regionserver.TestHStore.doWriteTestLargeCellAndSmallCellConcurrently(TestHStore.java:1919)
> at
> org.apache.hadoop.hbase.regionserver.TestHStore.testCompactingMemStoreWriteLargeCellAndSmallCellConcurrently(TestHStore.java:1819)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> ....
> {code}
> There is no {{Assert}} in {{TestHStore.java:1919}}, the {{AssertionError}} is
> thrown by method called by
> {{TestHStore.doWriteTestLargeCellAndSmallCellConcurrently}}, the error stack
> trace which actually throws {{AssertionError}} is trimmed by
> {{maven-surefire-plugin}} because of the default setting, just see
> [trimStackTrace|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#trimStackTrace]
> .
> If I turned off the {{trimStackTrace}}, the whole stack trace is displayed,
> which is convenient to locate the root cause:
> {code:java}
> [ERROR]
> org.apache.hadoop.hbase.regionserver.TestHStore.testCompactingMemStoreWriteLargeCellAndSmallCellConcurrently
> Time elapsed: 0.44 s <<< FAILURE!
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:87)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at org.junit.Assert.assertTrue(Assert.java:53)
> at
> org.apache.hadoop.hbase.regionserver.TestHStore$MyCompactingMemStore3.flushInMemory(TestHStore.java:2267)
> at
> org.apache.hadoop.hbase.regionserver.CompactingMemStore.tryFlushInMemoryAndCompactingAsync(CompactingMemStore.java:460)
> at
> org.apache.hadoop.hbase.regionserver.CompactingMemStore.checkAndAddToActiveSize(CompactingMemStore.java:446)
> at
> org.apache.hadoop.hbase.regionserver.TestHStore$MyCompactingMemStore3.checkAndAddToActiveSize(TestHStore.java:2238)
> at
> org.apache.hadoop.hbase.regionserver.CompactingMemStore.preUpdate(CompactingMemStore.java:317)
> at
> org.apache.hadoop.hbase.regionserver.AbstractMemStore.doAddOrUpsert(AbstractMemStore.java:149)
> at
> org.apache.hadoop.hbase.regionserver.AbstractMemStore.add(AbstractMemStore.java:122)
> at org.apache.hadoop.hbase.regionserver.HStore.add(HStore.java:730)
> at
> org.apache.hadoop.hbase.regionserver.TestHStore.doWriteTestLargeCellAndSmallCellConcurrently(TestHStore.java:1919)
> at
> org.apache.hadoop.hbase.regionserver.TestHStore.testCompactingMemStoreWriteLargeCellAndSmallCellConcurrently(TestHStore.java:1819)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> .....
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
