From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: do people find t5504.8 flaky?
Date: Mon, 29 Apr 2019 09:36:25 -0400 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1904290927210.45@tvgsbejvaqbjf.bet> (raw)
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
prev parent reply other threads:[~2019-04-29 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 2:45 do people find t5504.8 flaky? Junio C Hamano
2019-04-23 3:02 ` Jeff King
2019-11-13 0:07 ` SZEDER Gábor
2019-11-13 1:03 ` Jeff King
2019-11-13 2:07 ` Jeff King
2019-11-18 22:30 ` SZEDER Gábor
2019-11-18 23:25 ` Randall S. Becker
2019-11-13 3:47 ` Junio C Hamano
2019-04-29 13:36 ` Johannes Schindelin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1904290927210.45@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).