You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Shaker (Jira)" <ji...@apache.org> on 2020/12/18 14:14:00 UTC

[jira] [Created] (HDDS-4613) Flaky Test

Shaker created HDDS-4613:
----------------------------

             Summary: Flaky Test
                 Key: HDDS-4613
                 URL: https://issues.apache.org/jira/browse/HDDS-4613
             Project: Hadoop Distributed Data Store
          Issue Type: Bug
          Components: test
    Affects Versions: 1.0.0
            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 ozone project and found the following likely flaky tests:
 * testContainerThrottle

We sincerely hope that this can be useful information and look forward to hearing back.

 

 

[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)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org