[ 
https://issues.apache.org/jira/browse/HBASE-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563647#comment-13563647
 ] 

Ted Yu commented on HBASE-7681:
-------------------------------

>From 
>https://builds.apache.org/job/HBase-0.94/781/testReport/org.apache.hadoop.hbase.regionserver/TestAtomicOperation/testRowMutationMultiThreads/:
{code}
2013-01-26 19:53:55,720 INFO  [Thread-114] regionserver.Store(1129): Completed 
major compaction of 4 file(s) in colfamily11 of 
testtable,,1359230031766.0e4657859f8ff751b545ee6dfd92446e. into 
29f808fd896d4b78ae69c40e36ab2f1e, size=731.0; total size for store is 731.0
2013-01-26 19:53:55,721 DEBUG [Thread-109] 
regionserver.TestAtomicOperation$1(307): 
keyvalues={rowA/colfamily11:qual1/3830/Put/vlen=6/ts=4062, 
rowA/colfamily11:qual2/3838/Put/vlen=6/ts=0}
Exception in thread "Thread-109" junit.framework.AssertionFailedError   at 
junit.framework.Assert.fail(Assert.java:48)
        at junit.framework.Assert.fail(Assert.java:56)
        at 
org.apache.hadoop.hbase.regionserver.TestAtomicOperation$1.run(TestAtomicOperation.java:309)
{code}
This was due to more than one column being visible:
{code}
              // check: should always see exactly one column
              Get g = new Get(row);
              Result r = region.get(g, null);
              if (r.size() != 1) {
                LOG.debug(r);
                failures.incrementAndGet();
                fail();
{code}
                
> Investigate recent random test failures in 0.94
> -----------------------------------------------
>
>                 Key: HBASE-7681
>                 URL: https://issues.apache.org/jira/browse/HBASE-7681
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>             Fix For: 0.94.5
>
>         Attachments: 7681-0.94-combined.txt, 7681-0.94.txt, 7681-94-v1.txt, 
> 7681-94-v2.txt, 7681-94-v3.txt, 7681-trunk-v1.txt
>
>
> I've seen many unspecific test failures recently that cannot be reproduced 
> locally even when running these test is a loop for a very long time.
> Many of these test one way or the other make assumption w.r.t. wall clock 
> time. While I cannot fix that, an option to increase some of these timeout a 
> bit.
> This issue is to remind me to do that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to