This is a bug repository that keeps growing, called growingBugs
Notably, each bug in growingBugs is composed of a buggy version, a fixed version, a concise patch (bug-fixing changes only), and one or more triggering test cases.
Contents of growingBugs
To date, growingBugs contains 1911 real-world bugs from open-source Java projects.
Download the project repositories and external libraries that are not included in the git repository for size purposes and to avoid redundancies. We provide a mechanism to download them automatically as follows:
Notably, GrowingBugs supports sub-projects that are not suported by Defects4J. To this end, yor should specify the sub-project with -s parameter in the checkout command. The preceding example common leverages -s core to check out sub-proejct core from the enclosing project Shiro_core. For the compile and test commands, you should also switch to the sub-project’s folder to compile and test the sub-project.
Change to the working directory, compile sources and tests, and run tests:
cd work_dir/subproject_locator
defects4j compile
defects4j test
Example1:
cd /tmp/Shiro_core_37_buggy/core
defects4j compile
defects4j test
Example2:
cd /tmp/dbutils_1_buggy
defects4j compile
defects4j test
Currently, we resuse all APIs of Defects4J (more details at https://github.com/rjust/defects4j), and thus all applications relying on Defects4J could be transferred smoothly to GrowingBugs.
Docker Image
To free users (especially beginers) of the repository from the complex configuration of the environments, we create and publish a Docker image of the system. You may download it by the following command:
By simply loading the image with Docker, you can make the system ready for evaluation where all configurations (e.g., Java versions, paths, and even all data within the repository) should have been well set.
Versions
Because the bug repository keeps growing, let us known if you need a stable version for your study (e.g., evalutions for a research paper), and we will release a specific version where the bugs and patches are fixed (to faciliate the replication of your study).
Copyright
Notably, this bug repository is based on the well-known Defects4Jhttps://github.com/rjust/defects4j. We reuse its source code as well as the bugs in Defects4J. The key difference is that growingBugs levearages BugBuilder[1] to exclude bug-irrelevarange changes from bug-fixing commmits automatically whereas Defects4J requests human experts to accomplish the same task. Consequently, growingBugs can keep growing automatically even without human intervention.
Citation
If you are exploiting our dataset, please kindly cite the following paper:
[2]Yanjie Jiang, Hui Liu*, Xiaoqing Luo, Zhihao Zhu, Xiaye Chi, Nan Niu, Yuxia Zhang, Yamin Hu, Pan Bian, and Lu Zhang. “ BugBuilder: An Automated Approach to Building Bug Repository,” in IEEE Transactions on Software Engineering, Online 2022, doi: 10.1109/TSE.2022.3177713
[3]Yanjie Jiang, Hui Liu*,Yuxia Zhang, Weixing Ji, Hao Zhong, and Lu Zhang. “Do Bugs Lead to Unnaturalness of Source Code?” In Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE 2022). Association for Computing Machinery, New York, NY, USA, 1085–1096. https://doi.org/10.1145/3540250.3549149
@INPROCEEDINGS {GrowingBugsICSE21, author = {Yanjie Jiang and Hui Liu and Nan Niu and Lu Zhang and Yamin Hu}, booktitle = {IEEE/ACM 43rd International Conference on Software Engineering (ICSE 2021)}, title = {Extracting Concise Bug-Fixing Patches from Human-Written Patches in Version Control Systems}, year = {2021}, pages = {686-698}, doi = {10.1109/ICSE43902.2021.00069}, url = {https://doi.ieeecomputersociety.org/10.1109/ICSE43902.2021.00069}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, month = {may} }
@ARTICLE{GrowingBugsTSE2022, author={Jiang, Yanjie and Liu, Hui and Luo, Xiaoqing and Zhu, Zhihao and Chi, Xiaye and Niu, Nan and Zhang, Yuxia and Hu, Yamin and Bian, Pan and Zhang, Lu}, journal={IEEE Transactions on Software Engineering}, title={BugBuilder: An Automated Approach to Building Bug Repository}, year={2022}, volume={}, number={}, pages={1-22}, doi={10.1109/TSE.2022.3177713}}
@inproceedings{NaturalnessOfBugsFSE2022, author = {Jiang, Yanjie and Liu, Hui and Zhang, Yuxia and Ji, Weixing and Zhong, Hao and Zhang, Lu}, title = {Do Bugs Lead to Unnaturalness of Source Code?}, year = {2022}, isbn = {9781450394130}, publisher = {Association for Computing Machinery}, address = {New York, NY, USA}, url = {https://doi.org/10.1145/3540250.3549149}, doi = {10.1145/3540250.3549149}, booktitle = {Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering}, pages = {1085–1096}, numpages = {12}, keywords = {Naturalness, Source Code, Bug Fixing, Bugs, Code Entropy}, location = {Singapore, Singapore}, series = {ESEC/FSE 2022} }
Table of Contents
General Introduction
This is a bug repository that keeps growing, called growingBugs
Notably, each bug in growingBugs is composed of a buggy version, a fixed version, a concise patch (bug-fixing changes only), and one or more triggering test cases.
Contents of growingBugs
To date, growingBugs contains
1911
real-world bugs from open-source Java projects._plugin
-plugin
/core/api
_compiler
drools-model-compiler
_plugin
filevault
_vault_core
filevault_vault
_validation
Binary_cbor
-binary-cbor
Binary_protobuf
-binary-protobuf
_core
doxia-module-apt
clustering_java
clustering-java
_core_h2
_core_httpcore5
-angle
_vault_validation
-vault-validation
_plugin
-plugin
_core
_java8_datetime
-java8-datetime
Text_yaml
-text-yaml
Text_properties
-text-properties
Binary_avro
-binary-avro
JsonSchema
jsonSchema
typeJoda
Jsr310
Binary_smile
-binary-smile
Afterburner
salesforce
server_container
_core
container-core
_core
_api
-tamaya-api
mailet_standard
mailet-standard
jsonschema
mapper
_commons_editor
_backend
/uberfire-commons-editor/
uberfire-commons-editor-backend
commons
kie-pmml-commons
compiler
_task_workitems
jbpm-human-task-workitems
security_management_client
/uberfire-security
/uberfire-security-management
/uberfire-security
-management-client
_workbench_client
uberfire-workbench-client
_java_kie_wb
_common_stunner
_widgets
stunner-widgets
kie-wb-common-stunner-client/
kie-wb-common-stunner-widgets
validation
config
validate
_client
_common
/rave-core
/rave-commons
container
_webhook
retired_pirk
ions_generator
-generator
postreceive
_webhook
-postreceive-webhook
benchmark
_notifier
build-notifier
_authenticator
_authenticator
concurrent
thread_local
-thread-local
_support
-support
_toolkit
-toolkit
mqtt_cs
_format_core
-format-core
_code_java
-code-java
annotations
_hibernate4
-hibernate4
Setting up GrowingBugs
Requirements
Steps to set up GrowingBugs
Clone GrowingBugs:
git clone https://github.com/liuhuigmail/GrowingBugRepository.git
Initialize GrowingBugs:
Download the project repositories and external libraries that are not included in the git repository for size purposes and to avoid redundancies. We provide a mechanism to download them automatically as follows:
cd GrowingBugRepository
cpanm --installdeps .
./init.sh
./repos.sh
Add GrowingBugs’s executables to your PATH:
export PATH=$PATH:"path2growingbugs"/framework/bin
Using GrowingBugs
Typical Usage
Checkout a buggy source code version (If the project doesn’t hava subproject,
-s
parameter can be ignored):defects4j checkout -p project_id -v version_id -w work_dir -s subproject_locator
Example:
defects4j checkout -p Shiro_core -v 37b -w /tmp/Shiro_core_37_buggy -s core
defects4j checkout -p Dbutils -v 1b -w /tmp/dbutils_1_buggy
Notably, GrowingBugs supports sub-projects that are not suported by Defects4J. To this end, yor should specify the sub-project with
-s
parameter in thecheckout
command. The preceding example common leverages-s core
to check out sub-proejctcore
from the enclosing projectShiro_core
. For thecompile
andtest
commands, you should also switch to the sub-project’s folder to compile and test the sub-project.Change to the working directory, compile sources and tests, and run tests:
cd work_dir/subproject_locator
defects4j compile
defects4j test
Example1:
cd /tmp/Shiro_core_37_buggy/core
defects4j compile
defects4j test
Example2:
cd /tmp/dbutils_1_buggy
defects4j compile
defects4j test
Currently, we resuse all APIs of Defects4J (more details at https://github.com/rjust/defects4j), and thus all applications relying on Defects4J could be transferred smoothly to GrowingBugs.
Docker Image
To free users (especially beginers) of the repository from the complex configuration of the environments, we create and publish a Docker image of the system. You may download it by the following command:
docker pull registry.cn-hangzhou.aliyuncs.com/bit-zhuzhihao/growingbugrepository:0.3
By simply loading the image with Docker, you can make the system ready for evaluation where all configurations (e.g., Java versions, paths, and even all data within the repository) should have been well set.
Versions
Because the bug repository keeps growing, let us known if you need a stable version for your study (e.g., evalutions for a research paper), and we will release a specific version where the bugs and patches are fixed (to faciliate the replication of your study).
Copyright
Notably, this bug repository is based on the well-known Defects4J https://github.com/rjust/defects4j. We reuse its source code as well as the bugs in Defects4J. The key difference is that growingBugs levearages BugBuilder[1] to exclude bug-irrelevarange changes from bug-fixing commmits automatically whereas Defects4J requests human experts to accomplish the same task. Consequently, growingBugs can keep growing automatically even without human intervention.
Citation
If you are exploiting our dataset, please kindly cite the following paper:
[1] Yanjie Jiang, Hui Liu*, Nan Niu, Lu Zhang, Yamin Hu. Extracting Concise Bug-Fixing Patches from Human-Written Patches in Version Control Systems. The 43rd International Conference on Software Engineering (ICSE), pp. 686-698, May, 2021
[2]Yanjie Jiang, Hui Liu*, Xiaoqing Luo, Zhihao Zhu, Xiaye Chi, Nan Niu, Yuxia Zhang, Yamin Hu, Pan Bian, and Lu Zhang. “ BugBuilder: An Automated Approach to Building Bug Repository,” in IEEE Transactions on Software Engineering, Online 2022, doi: 10.1109/TSE.2022.3177713
[3]Yanjie Jiang, Hui Liu*,Yuxia Zhang, Weixing Ji, Hao Zhong, and Lu Zhang. “Do Bugs Lead to Unnaturalness of Source Code?” In Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE 2022). Association for Computing Machinery, New York, NY, USA, 1085–1096. https://doi.org/10.1145/3540250.3549149
@INPROCEEDINGS {GrowingBugsICSE21, author = {Yanjie Jiang and Hui Liu and Nan Niu and Lu Zhang and Yamin Hu}, booktitle = {IEEE/ACM 43rd International Conference on Software Engineering (ICSE 2021)}, title = {Extracting Concise Bug-Fixing Patches from Human-Written Patches in Version Control Systems}, year = {2021}, pages = {686-698}, doi = {10.1109/ICSE43902.2021.00069}, url = {https://doi.ieeecomputersociety.org/10.1109/ICSE43902.2021.00069}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, month = {may} }
@ARTICLE{GrowingBugsTSE2022, author={Jiang, Yanjie and Liu, Hui and Luo, Xiaoqing and Zhu, Zhihao and Chi, Xiaye and Niu, Nan and Zhang, Yuxia and Hu, Yamin and Bian, Pan and Zhang, Lu}, journal={IEEE Transactions on Software Engineering}, title={BugBuilder: An Automated Approach to Building Bug Repository}, year={2022}, volume={}, number={}, pages={1-22}, doi={10.1109/TSE.2022.3177713}}
@inproceedings{NaturalnessOfBugsFSE2022, author = {Jiang, Yanjie and Liu, Hui and Zhang, Yuxia and Ji, Weixing and Zhong, Hao and Zhang, Lu}, title = {Do Bugs Lead to Unnaturalness of Source Code?}, year = {2022}, isbn = {9781450394130}, publisher = {Association for Computing Machinery}, address = {New York, NY, USA}, url = {https://doi.org/10.1145/3540250.3549149}, doi = {10.1145/3540250.3549149}, booktitle = {Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering}, pages = {1085–1096}, numpages = {12}, keywords = {Naturalness, Source Code, Bug Fixing, Bugs, Code Entropy}, location = {Singapore, Singapore}, series = {ESEC/FSE 2022} }