Shaker created HBASE-25408:
------------------------------
Summary: Flaky Test
Key: HBASE-25408
URL: https://issues.apache.org/jira/browse/HBASE-25408
Project: HBase
Issue Type: Bug
Components: flakies, integration tests, test
Affects Versions: 2.3.2
Reporter: Shaker
Hello, we are a group of researchers interested in understanding methods to
reduce costs associated with Test Flakiness [1]. We developed an approach to
detect flaky tests, dubbed Shaker [2]. Shaker spawns stressor tasks in the
running environment (e.g., tasks that consume lots of cpu or memory) to
identify if perturbations can make tests fail.
We ran Shaker on hbase project and found the following likely flaky tests:
*
org.apache.hadoop.hbase.io.hfile.bucket.TestVerifyBucketCacheFile.testRetrieveFromFile
- failed 5 times in 12 reruns.
org.apache.hadoop.hbase.io.hfile.TestLruBlockCache.testBackgroundEvictionThread
- failed 4 times in 12 reruns.
org.apache.hadoop.hbase.master.normalizer.TestRegionNormalizerWorkQueue.testTake
- failed 1 time in 12 reruns.
[Denini|https://github.com/denini08], [Leopoldo|https://github.com/leopoldomt]
and [Marcelo|https://github.com/damorim].
[1] [https://hackernoon.com/flaky-tests-a-war-that-never-ends-9aa32fdef359]
[2] D. Silva, L. Teixeira and M. d’Amorim, "Shake It! Detecting Flaky Tests
Caused by Concurrency with Shaker," _2020 IEEE International Conference on
Software Maintenance and Evolution (ICSME)_, Adelaide, Australia, 2020, pp.
301-311, [https://ieeexplore.ieee.org/document/9240694/].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
