Repairnator's operation diagram when running on Travis's continuous integration service.
Repairnator has undergone two tests. For the first time from February to December 2017, Repairnator was run to search for errors on a list of about 14,188 GitHub projects. The results showed that Repairnator analyzed more than 11,500 builds with errors, including 3,000 cases where it could reproduce bugs and develop patches for 15 cases. However, since Repairnator patches are too low quality or late, not all are accepted into the build.
The researchers found that the prototype of the bot program could fix about 30 bugs every day.
The second test took place from January until June 2018, and brought more success. This time, Repairnator is set up to be able to work on Travis's continuous integration service. On January 21, Repairnator had a patch approved by the human censor for inclusion in the build. In the next 6 months, 5 other patches written by Repairnator were also accepted by human censors. This proves, Repairnator has been able to compete with people.
Repairnator's success is a milestone that paves the way for a new generation of software development. However, it also entails a host of new issues that need to be addressed such as who manages and owns intellectual property and is responsible for the bot program's contributions.
Perhaps people will have to answer these questions before people and machines can collaborate more.
Monperrus and colleagues believe that in the future, bots and people can collaborate smoothly and even collaborate in creating software.