From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>,
"'Jean-Noël AVILA'" <jn.avila@free.fr>
Cc: <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.32.0-rc1 - Defect in t0301.3, t1092.6, t5300
Date: Mon, 24 May 2021 18:37:29 -0400 [thread overview]
Message-ID: <036b01d750ed$642b75c0$2c826140$@nexbridge.com> (raw)
>Subject: Re: [ANNOUNCE] Git v2.32.0-rc1
On running the test suite on NonStop, t1092 fails in subtest 6 - but not when run with --verbose and -x, so I can't supply a log. This may be timing related. I wanted to report this in case anyone had any insight on whether there are any possible transient vulnerabilities. t0301.3 often has transient failures - which has been experienced for a while. Most importantly, t5300 continues to fail completely on the x86 platform, but not ia64, which I previously reported.
-Randall
next reply other threads:[~2021-05-24 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 22:37 Randall S. Becker [this message]
2021-05-24 22:44 ` [ANNOUNCE] Git v2.32.0-rc1 - Defect in t0301.3, t1092.6, t5300 Taylor Blau
2021-05-25 13:17 ` Randall S. Becker
2021-05-25 15:09 ` Taylor Blau
2021-05-25 15:28 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='036b01d750ed$642b75c0$2c826140$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jn.avila@free.fr \
/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).