Open Amirfarhad-Nilizadeh opened 3 years ago
Hi @Amirfarhad-Nilizadeh
when I add some more tests to the test suite, then after around 45 seconds, it cannot generate a patch
I should see the log to see what is happening. Could you create a PR with a test case that exercise that behaviour.
Does any option consider managing the time to execute a candidate patch?
Yes, see, for example, here: https://github.com/SpoonLabs/astor/blob/master/docs/arguments.md#validation
Thanks Matias
Hi @martinezmatias Thank you for your quick response. You can find a buggy program with two different test suites (the smaller test suite is the subset of the larger one) and reports of jGenProg for each one.
jGenProg can repair the buggy program with the smaller ones but cannot fix it with the larger test suite. Also, the program has only one bug, which is in line 245.
Hi @martinezmatias
Did you have a chance to look at attached examples in the zip file? Please let me know if I should provide them differently.
Thank you for your time and consideration in advance.
Best Wishes, Amirfarhad
Hi @Amirfarhad-Nilizadeh
Could you create a PR with a failing test case that exercise this example you attach?
Regards Matias
Three buggy programs in a BuggyJava+JML dataset can be repaired correctly with a test suite using jGenProg in about 50 seconds. However, when I add some more tests to the test suite, then after around 45 seconds, it cannot generate a patch (correct or overfitted).
What can be the reason?
Is there any time limitation for running a candidate patch to validate it in the Astor framework? Maybe this time is not enough to run the larger test suite for each candidate patch. Does any option consider managing the time to execute a candidate patch?