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

Hudson commented on HBASE-28976:
--------------------------------

Results for branch branch-3
        [build #336 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/336/]: 
(/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/336/General_20Nightly_20Build_20Report/]








(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/336/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop ${HADOOP_THREE_VERSION} backward compatibility 
checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/336/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop ${HADOOP_THREE_VERSION} backward compatibility 
checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/336/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop ${HADOOP_THREE_VERSION} backward compatibility 
checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/336/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.1 {color}


> Fix UT flakeyness in TestBucketCache.testBlockAdditionWaitWhenCache and 
> TestVerifyBucketCacheFile.testRetrieveFromFile
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-28976
>                 URL: https://issues.apache.org/jira/browse/HBASE-28976
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 3.0.0-beta-1, 2.7.0, 2.6.1, 2.5.10
>            Reporter: Wellington Chevreuil
>            Assignee: Wellington Chevreuil
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>
> Noticed these two tests failing intermittently on some of the pre-commit 
> runs. 
> 1) TestBucketCache.testBlockAdditionWaitWhenCache: The test calls 
> BucketCache.cacheBlock() passing true to the waitWhenCache parameter, 
> assuming the cache call will wait for a success cache, however this is only 
> true if the BucketCache.QUEUE_ADDITION_WAIT_TIME property is also defined, so 
> I believe this may be causing the intermittent failures when the pre-commit 
> runs on slower vms.
>  
> 2) TestVerifyBucketCacheFile.testRetrieveFromFile: One of the checks 
> performed by this test is to delete the bucket cache file, shutdown the 
> current BucketCache instance, then create a new BucketCache instance that 
> would load the persistent file but should fail to recover the cache, as the 
> cache file has been deleted. The way this recover works, internally, is 
> async. We first read the contents of the persistent file, which includes the 
> last serialized backingMap and a checksum of the cache file at that time. It 
> then compares this recovered checksum against the current cache file 
> checksum. If this verification fails, it starts a background thread to 
> traverse all backingMap entries and check if those entries are still 
> available in the cache. At this point, the test is ready to check the 
> BucketCache allocator size, expecting it to be 0, but if the background 
> verification has not finished yet, this assert will fail.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to