All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: 'Junio C Hamano' <gitster@pobox.com>,
	git@vger.kernel.org, szeder.dev@gmail.com,
	'Max Kirillov' <max@max630.net>
Subject: RE: [ANNOUNCE] Git v2.21.0-rc1 (NonStop Results)
Date: Thu, 14 Feb 2019 22:36:42 +0100 (STD)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1902142234070.45@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <001501d4c476$a94651d0$fbd2f570$@nexbridge.com>

Hi Randall,

On Thu, 14 Feb 2019, Randall S. Becker wrote:

> t5562 still hangs (blocking) - this breaks our CI pipeline since the
> test hangs and we have no explanation of whether the hang is in git or
> the tests.

I have "good" news: it now also hangs on Ubuntu 16.04 in Azure Pipelines'
Linux agents.

There is a silver lining with those good news, though: I found a
workaround, and it might work for you, too:

	https://github.com/gitgitgadget/git/pull/126

(I also submitted this to the Git mailing list, as I really wanted to tag
Git for Windows' v2.21.0-rc1.windows.1 only with a passing build, and I do
not want to keep that patch to the Windows port only.)

Ciao,
Johannes

  parent reply	other threads:[~2019-02-14 21:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 15:04 [ANNOUNCE] Git v2.21.0-rc1 (NonStop Results) Randall S. Becker
2019-02-14 19:56 ` Junio C Hamano
2019-02-14 21:36 ` Johannes Schindelin [this message]
2019-02-14 22:25   ` Randall S. Becker
2019-02-15 13:02   ` SZEDER Gábor
2019-02-15 13:49     ` Randall S. Becker
2019-02-15 20:37     ` Max Kirillov
2019-02-15 21:13       ` Randall S. Becker
2019-02-16  8:26         ` Max Kirillov
2019-02-18 20:50     ` [PATCH] t5562: chunked sleep to avoid lost SIGCHILD Max Kirillov
2019-02-18 20:54       ` Randall S. Becker
2019-02-18 20:59         ` Max Kirillov
2019-02-19 18:38       ` Junio C Hamano

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

* 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.1902142234070.45@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=max@max630.net \
    --cc=rsbecker@nexbridge.com \
    --cc=szeder.dev@gmail.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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.