Characterizing and predicting blocking bugs in open source projects

被引:29
|
作者
Valdivia-Garcia, Harold [1 ]
Shihab, Emad [2 ]
Nagappan, Meiyappan [3 ]
机构
[1] Bloomberg LP, New York, NY 10022 USA
[2] Concordia Univ, Montreal, PQ, Canada
[3] Univ Waterloo, Waterloo, ON, Canada
关键词
Process metrics; Code metrics; Post-release defects; SOFTWARE; METRICS; VALIDATION; ALGORITHMS; SEVERITY;
D O I
10.1016/j.jss.2018.03.053
中图分类号
TP31 [计算机软件];
学科分类号
081202 ; 0835 ;
摘要
Software engineering researchers have studied specific types of issues such reopened bugs, performance bugs, dormant bugs, etc. However, one special type of severe bugs is blocking bugs. Blocking bugs are software bugs that prevent other bugs from being fixed. These bugs may increase maintenance costs, reduce overall quality and delay the release of the software systems. In this paper, we study blocking bugs in eight open source projects and propose a model to predict them early on. We extract 14 different factors (from the bug repositories) that are made available within 24 hours after the initial submission of the bug reports. Then, we build decision trees to predict whether a bug will be a blocking bugs or not. Our results show that our prediction models achieve F-measures of 21%-54%, which is a two-fold improvement over the baseline predictors. We also analyze the fixes of these blocking bugs to understand their negative impact. We find that fixing blocking bugs requires more lines of code to be touched compared to non-blocking bugs. In addition, our file-level analysis shows that files affected by blocking bugs are more negatively impacted in terms of cohesion, coupling complexity and size than files affected by non-blocking bugs. (C) 2018 Published by Elsevier Inc.
引用
收藏
页码:44 / 58
页数:15
相关论文
共 50 条
  • [11] Predicting health indicators for open source projects (using hyperparameter optimization)
    Xia, Tianpei
    Fu, Wei
    Shu, Rui
    Agrawal, Rishabh
    Menzies, Tim
    EMPIRICAL SOFTWARE ENGINEERING, 2022, 27 (06)
  • [12] Predicting Popularity of Open Source Projects Using Recurrent Neural Networks
    Sahin, Sefa Eren
    Karpat, Kubilay
    Tosun, Ayse
    OPEN SOURCE SYSTEMS, OSS 2019, 2019, 556 : 80 - 90
  • [13] On Predicting the Time taken to Correct Bug Reports in Open Source Projects
    Anbalagan, Prasanth
    Vouk, Mladen
    2009 IEEE INTERNATIONAL CONFERENCE ON SOFTWARE MAINTENANCE, CONFERENCE PROCEEDINGS, 2009, : 523 - 526
  • [14] Predicting health indicators for open source projects (using hyperparameter optimization)
    Tianpei Xia
    Wei Fu
    Rui Shu
    Rishabh Agrawal
    Tim Menzies
    Empirical Software Engineering, 2022, 27
  • [15] An Empirical Validation of the Complexity of Code Changes and Bugs in Predicting the Release Time of Open Source Software
    Chaturvedi, K. K.
    Bedi, Punam
    Misra, Sanjay
    Singh, V. B.
    2013 IEEE 16TH INTERNATIONAL CONFERENCE ON COMPUTATIONAL SCIENCE AND ENGINEERING (CSE 2013), 2013, : 1201 - 1206
  • [16] Predicting Blocking Bugs with Machine Learning Techniques: A Systematic Review
    Brown, Selasie Aformaley
    Weyori, Benjamin Asubam
    Adekoya, Adebayo Felix
    Kudjo, Patrick Kwaku
    Mensah, Solomon
    INTERNATIONAL JOURNAL OF ADVANCED COMPUTER SCIENCE AND APPLICATIONS, 2022, 13 (06) : 674 - 683
  • [17] Predicting Fork Visibility Performance on Programming Language Interoperability in Open Source Projects
    Chua, Bee Bee
    INTERNATIONAL JOURNAL OF ADVANCED COMPUTER SCIENCE AND APPLICATIONS, 2018, 9 (01) : 32 - 37
  • [18] A Study of Concurrency Bugs in an Open Source Software
    Asadollah, Sara Abbaspour
    Sundmark, Daniel
    Eldh, Sigrid
    Hansson, Hans
    Enoiu, Eduard Paul
    OPEN SOURCE SYSTEMS: INTEGRATING COMMUNITIES, OSS 2016, 2016, 472 : 16 - 31
  • [19] Onboarding in Open Source Projects
    Fagerholm, Fabian
    Guinea, Alejandro Sanchez
    Borenstein, Jay
    Munch, Jurgen
    IEEE SOFTWARE, 2014, 31 (06) : 54 - 61
  • [20] Characteristics of open source projects
    Capiluppi, A
    Lago, P
    Morisio, M
    SEVENTH EUROPEAN CONFERENCE ON SOFTWARE MAINTENANCE AND REENGINEERING, PROCEEDINGS, 2003, : 317 - 327