Skip to content
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

Unrepair Math-84 #104

Closed
martinezmatias opened this issue Sep 24, 2021 · 4 comments
Closed

Unrepair Math-84 #104

martinezmatias opened this issue Sep 24, 2021 · 4 comments

Comments

@martinezmatias
Copy link
Collaborator

jGenProg arrives to repair with Gzoltar, but not with Flacoco (which does not fail)
Logs for the two executions, first Gzoltar, then Flacoco

https://github.com/martinezmatias/astor/runs/3676645094?check_suite_focus=true

@andre15silva
Copy link
Member

andre15silva commented Oct 3, 2021

This is not an issue with flacoco.

The location that is patched through GZoltar is the following:

location= org.apache.commons.math.optimization.direct.MultiDirectional
line= 90
lineSuspiciousness= 0.707

Flacoco identifies this line, with the same suspiciousness value: org.apache.commons.math.optimization.direct.MultiDirectional@-@90,0.7071067811865475

The difference is in the "priority". For GZoltar, this line is the 7th, whereas for Flacoco it is the 11th (cropped out the lines that appear after):

GZoltar:

org.apache.commons.math.optimization.direct.MultiDirectional l: 66, susp 0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional l: 69, susp 0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional l: 70, susp 0.7071067811865475
 org.apache.commons.math.optimization.direct.MultiDirectional l: 73, susp 0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional l: 74, susp 0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional l: 89, susp 0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional l: 90, susp 0.7071067811865475

Flacoco:

org.apache.commons.math.optimization.direct.MultiDirectional@-@45,0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional@-@46,0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional@-@47,0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional@-@48,0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional@-@66,0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional@-@69,0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional@-@70,0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional@-@73,0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional@-@74,0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional@-@89,0.7071067811865475
org.apache.commons.math.optimization.direct.MultiDirectional@-@90,0.7071067811865475

@monperrus
Copy link
Collaborator

Is that a timout issue then? (Astor does not have the time to reach the 11th line?

@andre15silva
Copy link
Member

Is that a timout issue then? (Astor does not have the time to reach the 11th line?

In this case yes (https://github.com/martinezmatias/astor/runs/3676645094?check_suite_focus=true#step:8:2326).

A similar issue might arise with the limit of generations.

@andre15silva
Copy link
Member

Closing as this is an issue in Astor SpoonLabs/astor#341

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants