eclipse / repairnator

Software development bots for Github. Join the bot revolution! :star2::robot::star2::revolving_hearts:

Repairnator: an open-source platform for software bots on Github

Repairnator is an open-source project for software bots on Github, in particular for automated program repair: build failure repair, static warning repair (SoraldBot), etc. The project is hosted at the Eclipse open-source foundation.

Eclipse/repairnator is a welcoming community :-) You're welcome to contribute, we have a number of open issues on which new contributors can jump in. Say hello!

Repairnator is done by a a nice team of welcoming engineers and researchers.

Documentation

The entry point to the documentation is https://github.com/eclipse/repairnator/blob/master/doc/README.md. The post "Repairnator patches programs automatically" gives a high-level overview of Repairnator.

Media coverage

See https://github.com/eclipse/repairnator/blob/master/doc/media.md.

Releases

• Maven releases: https://search.maven.org/search?q=repairnator
• DockerHub releases: https://hub.docker.com/r/repairnator/

License

The content of this repository is licensed under the MIT and the EPL licenses.

repairnator's Issues

Pushing builds into a repository.

For Bears, it'll be also necessary pushing builds (or parts of them) into a repository.

The issue is: do I push the builds for Bears into a (new) folder in the repository of builds for Repairnator (https://github.com/Spirals-Team/librepair-experiments) or do I create a new repository for this?

get the number of angelic values from Nopol

the presence of angelic values would show that we're on the right track and this would be encouraging

refactoring bear: filter projects in the passing/passing builds case

If two consequent builds are passing, we should filter them by getting the diff and looking if it concerns a test or not.

run reproduction & repair trial in asynchronous mode

eg in a separate Java process

Investigation on the use of other CI tools by projects.

feature: log languages of non-java scanned builds

Sometimes builds are inspected in current project list and not tagged as java build. It could be useful to know which languages and in which repo they are

bug: RepairNator is crashing when project have a large number of tests (>800K)

When building google/guava:

Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded
	at java.text.DecimalFormat.parse(DecimalFormat.java:2096)
	at java.text.NumberFormat.parse(NumberFormat.java:383)
	at org.apache.maven.plugins.surefire.report.TestSuiteXmlParser.startElement(TestSuiteXmlParser.java:170)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509)
	at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1339)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2784)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:841)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:770)
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:327)
	at org.apache.maven.plugins.surefire.report.TestSuiteXmlParser.parse(TestSuiteXmlParser.java:95)
	at org.apache.maven.plugins.surefire.report.TestSuiteXmlParser.parse(TestSuiteXmlParser.java:74)
	at org.apache.maven.plugins.surefire.report.SurefireReportParser.parseXMLReportFiles(SurefireReportParser.java:83)
	at fr.inria.spirals.repairnator.process.step.GatherTestInformation.businessExecute(GatherTestInformation.java:89)

Bug: push build step pushes more than 10 commits sometimes.

Clone project when missing commit is buggy

feature: parse pom.xml to detect src directory to NopolRepair stage

Some projects use a custom src directory which is then referenced in the pom.xml: when no source are find in standard directory, parse the pom.xml to find the correct directory to give it to Nopol.

Add the support for gradle

feature: send found patches to Twitter

Automate send of information to Twitter or Slack.

Refactoring: create an object to pass as input for the inspector of repairnator

Right now the scanner create a list of builds, but in the case of bears we want to get the current build, the previous one and the status (it is a case of failing/passing or passing/passing).
Then we should have an object containing all information to pass to the inspector to create the proper pipeline

feed bears spreadsheet automatically

... by also considering passing builds (to be discussed with @fermadeiral)

feature: add capability to clone repo even if the commit has been deleted

Delete commit which have been pushed on Github are still available through the API. Add a mechanism to retrieve them and use them to build.

Improve TravisFilter to be able to filter on the build tool (maven or gradle)

Are we losing lots of Android projects that can be interesting for us?

To be included in jtravis/parsers?

bug: sometimes travis request timeout breaking RepairNator

13:29:00.482 [main] DEBUG f.i.s.jtravis.helpers.LogHelper - Execute get request to the following URL: https://api.travis-ci.org/logs/146593459
13:29:10.486 [main] WARN  f.i.s.jtravis.helpers.LogHelper - Error when getting log id 146593459 : timeout
Exception in thread "main" java.lang.NullPointerException
	at fr.inria.spirals.repairnator.process.ProjectScanner.testBuild(ProjectScanner.java:210)
	at fr.inria.spirals.repairnator.process.ProjectScanner.getListOfBuildsFromRepo(ProjectScanner.java:239)
	at fr.inria.spirals.repairnator.process.ProjectScanner.getListOfBuildsFromProjectsByBuildStatus(ProjectScanner.java:159)
	at fr.inria.spirals.repairnator.process.ProjectScanner.getListOfFailingBuildFromProjects(ProjectScanner.java:146)
	at fr.inria.spirals.repairnator.Launcher.mainProcess(Launcher.java:302)
	at fr.inria.spirals.repairnator.Launcher.run(Launcher.java:249)
	at fr.inria.spirals.repairnator.Launcher.main(Launcher.java:399)

add time information in branch name on librepair-experiments

eg 20161216-1436

feature: use threads to launch bear

It should be useful to launch bear pipeline in distinct threads and to have a timeout on the whole pipeline.

feature: save reproducible, compilable, failing commits on github

push the merge commit on a specific branch

https://github.com/Spirals-Team/librepair-experiments

feature: add strategy in GatherTestInformation to explicit the contract

GatherTestInformation can have several different contracts depending on the pipeline goal and step, for example in the repair pipeline, it should stop the pipeline if no failing/error tests is found, but in bear pipeline it first should continue only if no fail/error is found, and then continue if a fail/error is found.
To be able to use a unique step you should add a strategy mechanism to the step to specify the contract.

Setup travis

add repairnator.properties and log in all existing branches of librepair-experiments

regression: passing java builds are not logged anymore

chore: create project librepair on INRIA forge

Create the pull requests automatically

Automate the fork and travis activation before pushing. PR remains manual.

add good repairnator.properties

goal: # of failures per day

# of failed builds per day
# of compilable failed builds per day
# of reproducible failed builds per day (ie with tests)
# of reproducible assertion-failed builds per day

(and per project)
leaderboard: top failing projects

We should distinguish "no test failing" and "test errors" states

RepairNator: parent pom are never reached

The URL build to get distant parent pom is wrong, so it cannot be retrieved:
i.e. POM org.apache:apache:10 try to get pom from: https://repo1.maven.org/maven2/org/apache/apache/org.apache:apache:pom:10/apache-org.apache:apache:pom:10.pom instead of https://repo1.maven.org/maven2/org/apache/apache/10/apache-10.pom

chore: create a cron to run Fernanda experiments

Do changes to push in the right repository cf #27

JSON serialization

Show information of reproduced build in a summary of the JSON distinguished with travis information.

Some maven invoker forks could consume all memory causing crash

Using RepairNator on prestodb project could lead to a crash as the mvn test command launches several mvn process which consumes all memory of the machine.
We should try to limit the memory consumption on the fork processes.

Get older builds from travis

feature: commit more information (repairnator.properties and log)

Repairnator.properties:
Add specific exception types and failing tests cases.
Execution time build & tests
Build information : user, repo, PR id, commit ID

Also commit maven.log containing all information about build & tests

regression: get error types back in Spreadsheet

jTravis feature: add previous failing/passing build for given ID

feature: automate the cleaning of workspace

Improve jTravis to detect the package manager used (Gradle or Maven)

bear: serialize process duration information

refactoring: clone repo with merging PR

Use this technique: https://help.github.com/articles/checking-out-pull-requests-locally/

regression: durations are not recorded anymore

refactoring: push repo should only take last 10 commits

jTravis: fix bug related to the usage of date depending on timezone

Travis is failing (see: https://travis-ci.org/Spirals-Team/librepair/builds/202171182) because of a date problem I did not encounter locally:

Failed tests: testGetBuildWithPR(fr.inria.spirals.jtravis.helpers.PRInformationHelperTest): expected:<PRInformation{head=CommitPojo{id='0', sha='567bbabd0c21214107dd8eb23edaf1e31c6ef1b3', branch='doc-typo-wording-fixes', message='Typo and wording fixes', committedAt=Tue Dec 27 18:59:07 UTC 2016, authorName='null', authorEmail='null', committerName='Lionel Seinturier', committerEmail='[email protected]', compareUrl='seintur/spoon@567bbabd0c21214107dd8eb23edaf1e31c6ef1b3'}, base=CommitPojo{id='0', sha='2b13f0f7e82f805b2480f6ff759b2d2e8debb493', branch='master', message='Typo: fixes a typo in doc/gradle.md', committedAt=Tue Dec 27 15:46:43 UTC 2016, authorName='null', authorEmail='null', committerName='Дмитрий', committerEmail='[email protected]', compareUrl='INRIA/spoon@2b13f0f7e82f805b2480f6ff759b2d2e8debb493'}, otherRepo=RepositoryPojo{id=27972573, slug='seintur/spoon', active=true, description='Spoon is a library for analyzing and transforming Java source code.', lastBuildId=0}}> but was:<PRInformation{head=CommitPojo{id='0', sha='567bbabd0c21214107dd8eb23edaf1e31c6ef1b3', branch='doc-typo-wording-fixes', message='Typo and wording fixes', committedAt=Tue Dec 27 17:59:07 UTC 2016, authorName='null', authorEmail='null', committerName='Lionel Seinturier', committerEmail='[email protected]', compareUrl='seintur/spoon@567bbabd0c21214107dd8eb23edaf1e31c6ef1b3'}, base=CommitPojo{id='0', sha='2b13f0f7e82f805b2480f6ff759b2d2e8debb493', branch='master', message='Typo: fixes a typo in doc/gradle.md', committedAt=Tue Dec 27 14:46:43 UTC 2016, authorName='null', authorEmail='null', committerName='Дмитрий', committerEmail='[email protected]', compareUrl='INRIA/spoon@2b13f0f7e82f805b2480f6ff759b2d2e8debb493'}, otherRepo=RepositoryPojo{id=27972573, slug='seintur/spoon', active=true, description='Spoon is a library for analyzing and transforming Java source code.', lastBuildId=0}}>

Apparently date are shifted one hour before. It should come from a different timezone on Travis server

Refactoring: gather methods related to git in a GitHelper class.

Dashboard

Size of librepair-experiments
Stats from spreadhseet (24h / 1 month / 1 week)

bug: push with 10 commits should commit first log/properties from repairnator

Use a docker machine by threads to apply a pipeline of steps

use chroot to use a specific environment for running commands

Spreadsheet: improve data displayed

Add the following information:

• Nopol Status (patch, timeout, exception...)
• PR URL if the build failed from a PR
• Test type of failures (AssertException, ...)
• Change color for rows containing test failures
• Add graph displaying reproduced build in the graph showing getting builds
• Add total time of running script