This dataset has been published in "SZZ in the time of Pull Requests" and is a collection of 11991 links from bug-introducing and bug-fixing commit sets extracted from Mozilla's Bugzilla (https://bugzilla.mozilla.org) with the use of bugbug.
In addition, the dataset also contains a set of 8906 links where the fix has not been found yet (so the bug-introducing commit set is known, but the bug-fixing commit set doesn't exist yet).
Bug IDs refer to Bugzilla bug reports, e.g. 1856572 is https://bugzilla.mozilla.org/show_bug.cgi?id=1856572.
Mercurial hashes refer to commits in the mozilla-central repository, e.g. 3c1db459589a845238abc0359c581fb436a9458f is https://hg.mozilla.org/mozilla-central/rev/3c1db459589a845238abc0359c581fb436a9458f.
Git hashes refer to commits in a clone of the mozilla-central repository using git-cinnabar: git clone hg::https://hg.mozilla.org/mozilla-central.
- Regressor / bug-introducing: a change in the repository, consisting of one or multiple commits, which causes a bug in the software.
- Regression: a bug caused by a bug-introducing change.
- Bug fix: a change in the repository, consisting of one or multiple commits, which resolves a bug in the software.
Note: a bug-fixing change can also be a bug-introducing change, and viceversa. Sometimes developers will fix bugs and introduce new ones in the process.
Run the example.py script with Python to see some high-level statistics about the dataset:
python example.pyThe output is:
Total number of pairs: 20897
Total number of pairs where both bug-introducing and bug-fix are known: 11991
Number of pairs with no shared files: 3126
Number of pairs where the bug-fix only contains new lines: 1869
Number of pairs where the bug-introducing only contains removed lines: 998
Number of pairs where the bug-introducing is not linked to any commit: 880
Number of bugs which are not fixed yet and where the cause has been identified: 8906
Deciles for the number of commits associated to bug fixes:
[0.0, 0.0, 0.0, 0.0, 1.0, 1.0, 1.0, 1.0, 2.0]
Deciles for the number of commits associated to bug introducing:
[1.0, 1.0, 1.0, 2.0, 2.0, 3.0, 4.0, 6.0, 12.0]
In this repository, you will find the dataset in two alternative formats:
- A CSV file containing all the information related to each issue
- A JSON file in a format compatible with PySZZ
In the CSV file, each record represents a link between a bug-introducing and a bug-fixing commit set, and it contains the following columns:
FIX_ID: the ID of the regression bug (bug linked to the bug-fixing commits) on BugzillaFIX_COMMITS_MERCURIAL: the list of bug-fixing commit hashes from the original Mozilla mozilla-central repository hosted in MercurialFIX_COMMITS_GIT: the list of bug-fixing commit hashes on the mozilla-central mirror git repository (see https://github.com/glandium/git-cinnabar)BUG_IDS: the IDs of the regressor bugs (bugs linked to the bug-introducing commits) on BugzillaBUG_COMMITS_MERCURIAL: the list of bug-introducing commit hashes from the original mozilla-central repository hosted in MercurialBUG_COMMITS_GIT: the list of fix-inducing commit hashes on the mozilla-central mirror git repositoryNO_FILE_SHARED: a boolean value.TRUEif no file is shared between the bug-fixing and bug-introducing commit sets (Extrinsic Bug/Ghost Commits),FALSEotherwise.NEW_LINES_ONLY_FIX: a boolean value.TRUEif there are only added lines in the bug-fixing commit-set (Ghost Commits),FALSEotherwise.REMOVE_LINES_ONLY_BUG: a boolean value.TRUEif there are only removed lines in the bug-introducing commit-set (Ghost Commits),FALSEotherwise.NO_BUG: a boolean value.TRUEif there is no commit linked to the regressor bug (Extrinsic Bug),FALSEotherwise.