Hi, On Mon, 13 Feb 2017, Junio C Hamano wrote:
> Johannes Schindelin <johannes.schinde...@gmx.de> writes: > > > That is why I taught the Git for Windows CI job that tests the four > > upstream Git integration branches to *also* bisect test breakages and > > then upload comments to the identified commit on GitHub > > Good. I do not think it is useful to try 'pu' as an aggregate and > expect it to always build and work [*1*], but your "bisect and > pinpoint" approach makes it useful to identify individual topic that > brings in a breakage. Sadly the many different merge bases[*1*] between `next` and `pu` (which are the obvious good/bad points for bisecting automatically) bring my build agents to its knees. I may have to disable the bisecting feature as a consequence. Ciao, Johannes Footnote *1*: There are currently 21, some of which stemming back from a year ago. For bisecting, they all have to be tested individually, putting a major dent into bisect's otherwise speedy process.
