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

Re: do people find t5504.8 flaky?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Apr 29, 2019, 13:36 UTC
Message-ID
<nycvar.QRO.7.76.6.1904290927210.45@tvgsbejvaqbjf.bet>
In-Reply-To
<xmqqmukh5tj6.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Tue, 23 Apr 2019, Junio C Hamano wrote:
> I have been seeing occasional failures of t5504-fetch-receive-strict
> test on the cc/replace-graft-peel-tags topic, but it seems that the
> fork point of that topic from the mainline already fails the same
> step #8, only less frequently.

Sounds familiar. IIRC it fails on Azure Pipelines from time to time, most often in linux-clang, less often in linux32. But I don't have hard data on that, I am still trying to get a grip on making the CI builds more robust without having to ask you to integrate azure-pipelines.yml changes into *all* branches.

Currently, my idea is to have two different Azure Pipelines set up: one that performs the continuous testing using azure-pipelines.yml on your maint, master, next and pu (do you want jch, too?) [*1*], and one that has a separate build definition and tries to work around many (all?) known issues with existing branches, e.g. coping with the known SIGPIPE issues in the git-daemon tests on macOS that *have* been addressed in master but not in some of the other branches that are accumulated into pu [*2*]. This latter build is *not* using azure-pipelines.yml, but a build definition that is maintained directly in Azure Pipelines ("Visual Designer" is what this feature is called in Azure Pipelines).

Ciao, Dscho

Footnote *1*: https://dev.azure.com/gitgitgadget/git/_build?definitionId=6
Footnote *2*: https://dev.azure.com/gitgitgadget/git/_build?definitionId=4
Previous: Junio C Hamano
Message 9 of 9 in “do people find t5504.8 flaky?”
  1. Junio C HamanoApr 23, 2019
  2. Jeff KingApr 23, 2019
  3. SZEDER GáborNov 13, 2019
  4. Jeff KingNov 13, 2019
  5. Jeff KingNov 13, 2019
  6. SZEDER GáborNov 18, 2019
  7. Randall S. BeckerNov 18, 2019
  8. Junio C HamanoNov 13, 2019
  9. Johannes SchindelinApr 29, 2019

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.