From: Max Kirillov <max@max630.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Randall S. Becker" <rsbecker@nexbridge.com>,
"'Max Kirillov'" <max@max630.net>,
"'SZEDER Gábor'" <szeder.dev@gmail.com>,
git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.21.0-rc1 (NonStop Results) - Good News
Date: Tue, 19 Feb 2019 22:15:36 +0200 [thread overview]
Message-ID: <20190219201536.GA2354@jessie.local> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1902182249140.45@tvgsbejvaqbjf.bet>
On Mon, Feb 18, 2019 at 10:57:13PM +0100, Johannes Schindelin wrote:
> I have to take that assessment back. So sad.
>
> After that build, I cherry-picked the commit on top of shears/pu (which is
> Git for Windows' ever-green branch that continuously rebases Git for
> Windows' `master` onto git.git's `pu`), and the build seems to hang again:
>
> https://dev.azure.com/git-for-windows/git/_build/results?buildId=31291
Hi.
You seem to be talking about the hang like it's some old
thing, I probably have missed some earlier discussion. I
have not heard before that it hangs on linux. The 60 seconds
hang because of lost SIGCHILD is not it. Also the hang
observed at NonStop is not it as well since the no-reuse
hack did not help (though numbered output files probably
would be more sure to avoid duplications expecially at
Windows where you cannot just unlink busy file and reuse its
place in directory)
From the tasks you have posted there seem to be no details
available. The test is not reported as completed, and the
overall build fails, and there seem to no additional data
except the log available.
Have you or somebody else been investigating it or is there
otherwise any information about those hangs?
--
Max
next prev parent reply other threads:[~2019-02-19 20:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 16:51 [ANNOUNCE] Git v2.21.0-rc1 (NonStop Results) - Good News Randall S. Becker
2019-02-16 17:02 ` Randall S. Becker
2019-02-16 18:05 ` Junio C Hamano
2019-02-16 18:24 ` Randall S. Becker
2019-02-16 18:57 ` Junio C Hamano
2019-02-18 18:45 ` Junio C Hamano
2019-02-18 18:50 ` Randall S. Becker
2019-02-19 10:05 ` Johannes Schindelin
2019-02-18 19:37 ` Johannes Schindelin
2019-02-18 21:57 ` Johannes Schindelin
2019-02-19 20:15 ` Max Kirillov [this message]
2019-02-19 20:36 ` Max Kirillov
2019-02-19 20:53 ` Randall S. Becker
2019-02-20 20:15 ` Johannes Schindelin
2019-02-18 20:24 ` Max Kirillov
2019-02-18 20:31 ` Randall S. Becker
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=20190219201536.GA2354@jessie.local \
--to=max@max630.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).