From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.27.0-rc0 - Results on HPE NonStop TNS/X
Date: Mon, 18 May 2020 13:07:21 -0400 [thread overview]
Message-ID: <02b701d62d36$ced15ec0$6c741c40$@nexbridge.com> (raw)
On May 14, 2020 7:28 PM, Junio C Hamano wrote:
> An early preview release Git v2.27.0-rc0 is now available for
> testing at the usual places. It is comprised of 479 non-merge
> commits since v2.26.0, contributed by 53 people, 16 of which are
> new faces.
All tests passed except, t9001 and t9020, which is normal.
t0301 subtest 8 (1x), 11 (3x), 12 (1x), 26 (2x), still randomly fail when run 10 times, but I can't reproduce any of the failures 100% of the time. Number of failures of each is listed. For 26, the removal of a socket is not instantaneous on a MPP system, so this may be partly at fault. It can take a few microseconds, which is less than the time it takes to execute that subtest from end-to-end. If the system is heavily loaded, the results are different. Checking that a file that was created is no longer there, unless you are doing an explicit rm in the same script, is not a good plan in this platform. It looks like that 'git credential-cache exit' may be happening in a different logical CPU from the test script so it takes non-zero time for the file system on the script's logical CPU to see the removal. If I stick a sleep 5 (to be paranoid) into subtest 26, the subtest becomes a stable pass.
Regards,
Randall
reply other threads:[~2020-05-18 17:07 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='02b701d62d36$ced15ec0$6c741c40$@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).