[HDDS-4613] testContainerThrottle is flaky

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Information Provided
• Affects Version/s: 1.0.0
• Component/s: test
• Labels: flaky-test test-failure
• Assignee: Unassigned
• Reporter: Shaker
• Created: 18/Dec/20 14:13
• Updated: 12/Jun/23 16:51
• Resolved: 12/Jun/23 16:51

Description

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, Leopoldo and Marcelo.

[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/.