search

program-repair / RepairThemAll

Automatic Repair Framework that abstract repair tools and bug benchmarks
MIT License
68 stars 23 forks source link

Does Closure use a different Fault Localization strategy compared with other projects in Defects4J #8

Open Kaka727 opened 5 years ago

Kaka727 commented 5 years ago

Hi @tdurieux I modified the source code of Arja according to your pull request and now I can run it. Thanks! I find another strange question. I can get the results among five projects except Closure in Defects4J. The log message is : image

I am very confused about that. We donot transfer a parameter named gzoltarDataDir. So according to the source code of ARJA, it should call GZoltarFaultLocalizer2 to perform FL. Why in the trace is GZoltarFaultLocalizer and why it fails. image

tdurieux commented 5 years ago

We did not use a different Fault Localization strategy. But I spent a bunch of in Nopol to configure gzoltar correctly for Closure. This project requires a really clean classpath to run the test.

Kaka727 commented 5 years ago

Does your pull request in arja reveal this configuration change? If not, how should I make the corresponding operation. I'm very confused.

tdurieux commented 5 years ago

I thought we faced the same issue during our executions but it is not the case, sorry about that.

I dont know what is happening exactly. It is related to the classpath or the java version, ... It can be because two different versions of JUnit is present in the classpath, or the java release version,...

Kaka727 commented 5 years ago

Just now I downloaded the docker image and run the command: docker run -it --rm -v /home/wp/Desktop/results:/results tdurieux/repairthemall Arja -b Defects4J -i Closure_1 The error is the same as I met in my own environment. image

I don't know why. It is very strange.