git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [git-for-windows] Re: Continuous Testing of Git on Windows

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 14, 2017, 20:55 UTC
Message-ID
<alpine.DEB.2.20.1702142150220.3496@virtualbox>
In-Reply-To
<xmqq60kdbqmy.fsf@gitster.mtv.corp.google.com>
Hi,
On Mon, 13 Feb 2017, Junio C Hamano wrote:
Show 10 quoted lines
> Johannes Schindelin <Johannes.Schindelin@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.

Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 19 in “Continuous Testing of Git on Windows”
  1. Johannes SchindelinFeb 10, 2017
  2. Junio C HamanoFeb 13, 2017
  3. Johannes SchindelinFeb 14, 2017
  4. Junio C HamanoFeb 14, 2017
  5. Christian CouderFeb 14, 2017
  6. Junio C HamanoFeb 14, 2017
  7. Philip OakleyFeb 14, 2017
  8. Junio C HamanoFeb 14, 2017
  9. Philip OakleyFeb 15, 2017
  10. Junio C HamanoFeb 15, 2017
  11. Philip OakleyFeb 15, 2017
  12. Junio C HamanoFeb 16, 2017
  13. Philip OakleyFeb 15, 2017
  14. Philip OakleyFeb 15, 2017
  15. Johannes SchindelinFeb 15, 2017
  16. Philip OakleyFeb 15, 2017
  17. Junio C HamanoFeb 16, 2017
  18. Philip OakleyFeb 18, 2017
  19. Johannes SchindelinFeb 15, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.