We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As far as I understood, GZoltar is used through Astor (https://github.com/eclipse/repairnator/blob/master/src/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/step/repair/sequencer/detection/AstorDetectionStrategy.java) in the sequenceR mode.
This means that, once SpoonLabs/astor#323 is merged, it will automatically use flacoco, as it will become the default fault localization mode.
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
FTR SpoonLabs/astor#323 is merged
Do we need to push a new version of Sequencer image on Dockerhub?
Yes, but before we need to release a new version of https://github.com/SpoonLabs/astor and a new version of repairnator. (see SpoonLabs/astor#333)
No branches or pull requests
As far as I understood, GZoltar is used through Astor (https://github.com/eclipse/repairnator/blob/master/src/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/step/repair/sequencer/detection/AstorDetectionStrategy.java) in the sequenceR mode.
This means that, once SpoonLabs/astor#323 is merged, it will automatically use flacoco, as it will become the default fault localization mode.
The text was updated successfully, but these errors were encountered: