-
Notifications
You must be signed in to change notification settings - Fork 83
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
new mode for fault-localization only #1029
Comments
Any suggestions?
1. Add a mode in the pipeline to have GZoltar fault localization only
2. Implement a Gitlab connector (with inspiration from the Jenkins connector
https://github.com/eclipse/repairnator/blob/master/doc/repairnator-jenkins-plugin.md)
|
Sorry ,could you please elaborate on the above points. Also, if astor is to be invoked in the pipeline , what's the procedure for that? |
No, this is not a use case we considered in the past.
See AstorRepair To achieve what you want, I'd suggest to study the different implementations of AbstractRepairStep and how they are used in ProjectInspector |
FTR, GZoltar has compatibility problems with recent JVMs, see SpoonLabs/nopol#211 |
The objective is on commit, it should build, then invoke Gzoltar to list the lines of code which are suspicious ..
Any suggestions???
The text was updated successfully, but these errors were encountered: