From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.33.0-rc1 (Build/Test Report)
Date: Wed, 11 Aug 2021 18:30:33 -0400 [thread overview]
Message-ID: <000801d78f00$832e98c0$898bca40$@nexbridge.com> (raw)
On August 6, 2021 8:07 PM, Junio C Hamano wrote:
>
>A release candidate Git v2.33.0-rc1 is now available for testing at the usual places. It is comprised of 396 non-merge commits since
>v2.32.0, contributed by 63 people, 19 of which are new faces [*].
Just a report that t0301.9 hung again on 2.32.0-rc1 on the NonStop ia64 platform, and t5563.8 hung on the x86 platform. These did not hang at rc0 or in 2.31.0. We have seen (and reported) these before and they do appear transient. I have been meaning to dig deeper into both of these tests to figure out why and what the conditions are, but there are many moving parts on the platform (it is MPP). It probably would take some brainstorming - I suspect there is something relating to timing in the message system that is causing this heartburn, but the features under test do not appear to be commonly used.
Really just an FYI.
-Randall
reply other threads:[~2021-08-11 22:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000801d78f00$832e98c0$898bca40$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--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.
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 NNTP newsgroup(s).