-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fault localization process fails when using CocoSpoonBasedSpectrumBasedFaultLocalizer
#179
Comments
Thanks for the report.
Can you provide us with a failing test case? (see test cases in nopl-core/src/test)
|
Could you create a pull request with only the failing test case? Thanks.
|
I have forked the nopol master branch into my github repo and then update the CocospoonLocalizerTest.java (#180). I then create a pull request with only the failing test case, with comments as follows:
More details can be seen at #180. (But in this website, the information Thank you for your continuous help! |
I am sorry, do I misunderstand your guidance (create a pull request with only the failing test case)? Should I create a new java file (e.g., called |
Closed, see #182 |
Sorry for disturbing you again with a new issue...
Previously, I used
GZoltarFaultLocalizer
to generate a rank list of suspicious statements when using Nopol to repair real bugs from defects4j.This time, I tried
CocoSpoonBasedSpectrumBasedFaultLocalizer
, which is also in the same folder ofGZoltarFaultLocalizer
(i.e.,src/main/java/fr/inria/lille/localization
), to localize faults. However, the error happens during running the tests. The detailed error info is:And as is shown in the log file:
I have made two attempts to study the reason behind the error:
1) I use Nopol with
CocoSpoonBasedSpectrumBasedFaultLocalizer
to repair the given example in the folder/Nopol/test-projects
, and the both the fault localization and repair process are successful (the expected patch is got). Therefore, I thought this error only occurs when usingCocoSpoonBasedSpectrumBasedFaultLocalizer
to repair real bugs in defects4j.To verify this thought, I use Nopol with
CocoSpoonBasedSpectrumBasedFaultLocalizer
to repair some bugs (e.g., chart 3, math 2, math 58), all of which get errors as mentioned above.2) By reviewing previous log files when using
GZoltarFaultLocalizer
, I found the same log infoDEBUG xxl.java.junit.TestSuiteExecution - Timeout after 5 seconds. Infinite loop?
commonly exists in previous logs that records how Nopol withGZoltarFaultLocalizer
repair real bugs (e.g., math 58) in defects4j. But these scenarios usingGZoltarFaultLocalizer
all successfully generate suspicious list of statements.Instead, the scenarios using
CocoSpoonBasedSpectrumBasedFaultLocalizer
stop and reportTimeoutException
.Much appreciated if any help is given.
The text was updated successfully, but these errors were encountered: