ACS: Accurate Condition Synthesis

Notification

ACS can no longer execute on new bugs. The execution of ACS requires querying of GitHub, but GitHub recently changed its interface and does not allow programmed queries. Therefore, the original code of ACS cannot execute normally and there is no easy way to fix that. ACS can still run on the original Defects4J bugs as the results were cached.

Our new tool L2S-Hanabi is a direct follow-up work of ACS and does not depend on external source. We recommend you to use L2S-Hanabi if you are seeking a tool fixing conditional bugs.

Tool: https://wangbo15.github.io/LingLong/
Paper: https://doi.org/10.1145/3487570

I. Requirement

Ubuntu14.04
Java 1.7
Python 2.7(need to install psutil)
Defects4J

II. How to run the ACS

Two optional: A. run the virtual machine; B. Set up the environment. Choose the way you like.

A. Run the virtual machine

If you do not want to set up the environment, please download the virtual machine, unzip and open it by VmWare12.5.2(username: yjxxtd, password: hhxxttxs).
There are 23 projects(18 correct and 5 incorrect) in the directory "/home/yjxxtd/software/defects4j-project/", the ACS is in the directory "/home/yjxxtd/software/ACS/ACS-master/".
Please run the run.sh in the directory "/home/yjxxtd/software/ACS/ACS-master/" to generate the 23 patches for the 23 projects.
If it does not work normaly, please increase the timeout time in the run.sh, for example "java -jar ACS.jar /home/yjxxtd/software/defects4j-project/ Chart_14 timeout:3600".

B. Set up the Environment

Clone the ACS:

git clone https://github.com/Adobee/ACS.git

Checkout a buggy source code version from Defects4j anc compile it:

defects4j checkout -p Lang -v 1b -w /tmp/Lang_1
cd /tmp/Lang_1
defects4j compile

the forder name of checkout must format as 'ProjectName_buggyID' because the ACS needs it's project name and buggy id to generate it's classpath, source path etc.

Run the Jar with the parent path of Defects4j buggy version project forder:

java -jar ACS.jar /tmp/

and ACS will automatically find all formatted folder and run with it.

Or run with specific buggy projects in /tmp/ forder(Note the space between "/tmp/" and "Lang_1"):

java -jar ACS.jar /tmp/ Lang_1
java -jar ACS.jar /tmp/ Lang_1;Lang_2;Lang_3
java -jar ACS.jar /tmp/ ban:Lang_1;Lang2

Or set a custom timeout seconds depends on your computer performance (default as 1800):

java -jar ACS.jar /tmp/ Lang_1 timeout:3600

III How to Build ACS

Althrough there is a pom.xml in the ACS, actually it's useless because of the difficulty of dependency configuration.

We prefer to use Intellij IDEA to build the ACS automatically.

'Open' the ACS project with Intellij IDEA, and ignore all warnings in the bottom right, such as 'Framework detected'.
There is a default configuration in the run/debug menu which named run ACS in the top right, click it and choose Edit configurations, replace the content in several input box according to its tip.
Click OK button, and use shortcut CTRL+F9 to build the project.

IV Tips

Tips of Chart19: After checkout from Defects4J, There are two itext jar files in Chart_19/lib folder and one of which named "itext-2.0.6.jar" is a broken jar and leads to the error of ACS, delete it and ACS would get back to normal.
The results are in the dir "ACS/resultMessage", the detailed patch is in the file "ACS/resultMessage/patchSource/Project_BugId_Schema_PatchId.java"(If a bug has n patches, the "PatchId" will range from 0 to n - 1), and is between "patch begin" and "patch end".
Please note that the patch file in the directory "ACS/resultMessage/patchSource/" does not mean it passes all the tests. If it fails to pass all the test, the patch file will be deleted if ACS has enough time. So if you want to know whether the patch file pass all the tests, please apply it in the source code, and test it manually by using the command "defects4j test".
There are some pictures in the dir "ACS/pictures" to show how to run the ACS.
If ACS didn't generate the patch or the patch is incomplete, it maybe cause by the performance of the computer, please increase the timeout time.

V. Evaluation

1.ACS Correct Patches

ACS generates correct patches for 17 defects. For each defect, we provide the urls that contain the developer patch and we either identify the ACS patch is semantically equivalent to the developer patch and provide a brief analysis for why the ACS patch is correct.

1).Chart14

The developer patches 1

The developer patches 2

The ACS correct patches 1

The ACS correct patches 2

Analysis:The ACS generated patch is identical to the developer patch.

Name		Name	Last commit message	Last commit date
Latest commit History 93 Commits
.idea		.idea
NLPModel		NLPModel
RunTestAgent		RunTestAgent
experiment		experiment
lib		lib
patch		patch
pictures		pictures
poster		poster
src		src
ACS.iml		ACS.iml
ACS.jar		ACS.jar
README.md		README.md
kill_process.py		kill_process.py
pom.xml		pom.xml

Adobee/ACS

Folders and files

Latest commit

History

Repository files navigation

ACS: Accurate Condition Synthesis

Notification

I. Requirement

II. How to run the ACS

A. Run the virtual machine

B. Set up the Environment

III How to Build ACS

IV Tips

V. Evaluation

1.ACS Correct Patches

1).Chart14

2).Chart19

3).Math3

4).Math4

5).Math5

6).Math25

7).Math35

8).Math61

9).Math82

10).Math85

11).Math89

12).Math90

13).Math93

14).Math99

15).Time15

16).Lang7

17).Lang24

2.ACS Incorrect Patches

1). Lang39

2). Math28

3). Math73

4). Math81

5). Math97

5).Lang35

3.Performance Data of the Three Techniques

About

Resources

Stars

Watchers

Forks

Releases

Packages 0

Contributors 5

Packages