Cross-Project Flakiness: A Case Study of the OpenStack Ecosystem
- 29 May 2026
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 52 (6) , 1875-1890
Abstract
Automated regression testing is a cornerstone of modern software development, often contributing directly to code review and Continuous Integration (CI). Yet some tests suffer from flakiness, where their outcomes vary non-deterministically. Flakiness erodes developer trust in test results, wastes computational resources, and undermines CI reliability. While prior research has examined test flakiness within individual projects, its broader ecosystem-wide impact remains largely unexplored. In this paper, we present an empirical study of test flakiness in the OpenStack ecosystem, which focuses on (1) cross-project flakiness, where flaky tests impact multiple projects, and (2) inconsistent flakiness, where a test exhibits flakiness in some projects but remains stable in others. By analyzing 649 OpenStack projects, we identify 1,535 cross-project flaky tests and 1,105 inconsistently flaky tests. We find that cross-project flakiness affects 55% of OpenStack projects and significantly increases both review time and computational costs. Surprisingly, 70% of unit tests exhibit cross-project flakiness, challenging the assumption that unit tests are inherently insulated from issues that span modules like integration and system-level tests. Through qualitative analysis, we observe that race conditions in CI, inconsistent build configurations, and dependency mismatches are the primary causes of inconsistent flakiness. These findings underline the need for better coordination across complex ecosystems, standardized CI configurations, and improved test isolation strategies.Keywords
All Related Versions
Funding Information
- JSPS for the KAKENHI (25K22845)
- JSPS for the KAKENHI (23KJ1589)
- JSPS for the KAKENHI (26H02500)
- JSPS for the KAKENHI (26K21198)
- Japan Science and Technology Agency (JPMJAP2415)
- Japan Science and Technology Agency (JST PRESTO)
- Japan Science and Technology Agency (JPMJPR22P6)
- NSERC through Alliance International Collaboration (ALLRP 580835-22)
This publication has 46 references indexed in Scilit:
- Rechecking Recheck Requests in Continuous Integration: An Empirical Study of OpenStack2025
- Repeated Builds During Code Review: An Empirical Study of the OpenStack Community2023
- Can we benchmark Code Review studies? A systematic mapping study of methodology, dataset, and metricJournal of Systems and Software, 2021
- Understanding shared links and their intentions to meet information needs in modern code review:Empirical Software Engineering, 2021
- Release synchronization in software ecosystemsEmpirical Software Engineering, 2021
- An empirical study of the impact of modern code review practices on software qualityEmpirical Software Engineering, 2015
- An empirical study of integration activities in distributions of open source softwareEmpirical Software Engineering, 2015
- Software ecosystems – A systematic literature reviewJournal of Systems and Software, 2013
- Dominance statistics: Ordinal analyses to answer ordinal questions.Psychological Bulletin, 1993
- Measuring nominal scale agreement among many raters.Psychological Bulletin, 1971