From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Taylor Blau'" <me@ttaylorr.com>
Cc: "'Junio C Hamano'" <gitster@pobox.com>,
"'Jean-Noël AVILA'" <jn.avila@free.fr>,
git@vger.kernel.org
Subject: RE: [ANNOUNCE] Git v2.32.0-rc1 - Defect in t0301.3, t1092.6, t5300
Date: Tue, 25 May 2021 09:17:40 -0400 [thread overview]
Message-ID: <037d01d75168$5a5aaea0$0f100be0$@nexbridge.com> (raw)
In-Reply-To: <YKwsSgtfhaGq5z8k@nand.local>
On May 24, 2021 6:44 PM, Taylor Blau wrote:
>To: Randall S. Becker <rsbecker@nexbridge.com>
>Cc: 'Junio C Hamano' <gitster@pobox.com>; 'Jean-Noël AVILA' <jn.avila@free.fr>; git@vger.kernel.org
>Subject: Re: [ANNOUNCE] Git v2.32.0-rc1 - Defect in t0301.3, t1092.6, t5300
>
>On Mon, May 24, 2021 at 06:37:29PM -0400, Randall S. Becker wrote:
>> 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.
>
>The failure in t1092 sounds should be addressed by
>
> https://lore.kernel.org/git/pull.960.git.1621886108515.gitgitgadget@gmail.com/
>
>> 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.
>
>Not sure about these, though.
Thanks will wait for the roll on that one. We had one loggable transient failure in t1096.15:
expecting success of 1092.15 'merge with outside renames':
init_repos &&
for type in out-to-out out-to-in in-to-out
do
test_all_match git reset --hard &&
test_all_match git checkout -f -b merge-$type update-deep &&
test_all_match git merge -m "$type" rename-$type &&
test_all_match git rev-parse HEAD^{tree} || return 1
done
+ init_repos
Updating files: 100% (14/14), done.
HEAD is now at 5d0e8a6 initial commit
Updating files: 100% (14/14), done.
HEAD is now at 5d0e8a6 initial commit
Updating files: 100% (14/14), done.
HEAD is now at 5d0e8a6 initial commit
Updating files: 100% (10/10), done.
Updating files: 100% (7/7), done.
Updating files: 100% (10/10), done.
Updating files: 100% (7/7), done.
+ test_all_match git reset --hard
+ test_all_match git checkout -f -b merge-out-to-out update-deep
+ test_all_match git merge -m out-to-out rename-out-to-out
--- full-checkout-err 2021-05-24 22:49:44 +0000
+++ sparse-checkout-err 2021-05-24 22:49:50 +0000
@@ -1 +0,0 @@
Updating files: 100% (5/5), done.
+ return 1
error: last command exited with $?=1
not ok 15 - merge with outside renames
#
# init_repos &&
#
# for type in out-to-out out-to-in in-to-out
# do
# test_all_match git reset --hard &&
# test_all_match git checkout -f -b merge-$type update-deep &&
# test_all_match git merge -m "$type" rename-$type &&
# test_all_match git rev-parse HEAD^{tree} || return 1
# done
#
next prev parent reply other threads:[~2021-05-25 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 22:37 [ANNOUNCE] Git v2.32.0-rc1 - Defect in t0301.3, t1092.6, t5300 Randall S. Becker
2021-05-24 22:44 ` Taylor Blau
2021-05-25 13:17 ` Randall S. Becker [this message]
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='037d01d75168$5a5aaea0$0f100be0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jn.avila@free.fr \
--cc=me@ttaylorr.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.