repairnator in A Sentence

    1

    Overall, the Repairnator project has fullfilled its mission.

    0
    2

    Overall, the Repairnator project has fulfilled its mission.

    0
    3

    In other words, Repairnator was human-competitive for the first time.

    0
    4

    We have been operating Repairnator since January 2017, in three different phases.

    0
    5

    Out of 3,551 repair attempts, Repairnator found 15 patches that could make the CI build pass.

    0
    6

    Repairnator's focus on build failures is unique, but it fits in the big picture of intelligent bots for software[2].

    0
    7

    From February 1st, 2017 to December 31th, 2017, we ran Repairnator with a fixed list of 14,188 projects, we call it“Expedition 1”.

    0
    8

    If it succeeds to synthesize a valid patch, Repairnator proposes the patch to the human developers, disguised under a fake human identity.

    0
    9

    To overcome this problem, we have decided early in the project that all Repairnator patches would be proposed under a fake human identity.

    0
    10

    That was the first patch produced by Repairnator and accepted as a valid contribution by a human developer, definitively merged in the code base.

    0
    11

    That was the first patch produced by Repairnator and accepted as a valid contribution by a human developer, definitively merged into the code base.

    0
    12

    To date, Repairnator has been able to produce 5 patches that were accepted by the human developers and permanently merged in the code base.

    0
    13

    On Jan 12th 2018, at 1:35pm, a Repairnator team member took the patch generated by Repairnator, and validated the opening of the corresponding pull-request on GitHub.

    0
    14

    However, our patch analysis revealed that none of those patches were human-competitive because they came too late(Repairnator produced a patch after the human developer) or were of low quality(they made the build successful coincidentally).

    0
    15

    In addition to showing that program repair is human competitive, the Repairnator project has provided a wealth of information about bugs and continuous integration, and about the current shortcomings of program repair research, presented in[7].

    0
    16

    The key idea of Repairnator is to automatically generate patches that repair build failures, then to show them to human developers, to finally see whether those human developers would accept them as valid contributions to the code base.

    0