From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.28.0-rc1
Date: Fri, 17 Jul 2020 17:21:10 -0400 [thread overview]
Message-ID: <00d001d65c80$3519c960$9f4d5c20$@nexbridge.com> (raw)
In-Reply-To: <xmqqv9ildh46.fsf@gitster.c.googlers.com>
On July 17, 2020 4:25 PM, Junio C Hamano Wrote:
> A release candidate Git v2.28.0-rc1 is now available for testing at the usual
> places. It is comprised of 295 non-merge commits since v2.27.0, contributed
> by 43 people, 10 of which are new faces.
The prior commit just before this one, and the rc0 commit both failed t3200.93 and t3200.97 on NonStop. This looks like a recurrence if the situation where a test was written assuming a specific error message that is different on the NonStop platform. The error in both causes is expecting "could not lock config file .git/config: File exists" which is not what the system reports. The strerror proc reports "File already exists".
A similar situation was previously discussed as part of fixes to t1901 (https://public-inbox.org/git/020c01d5f880$1cf7c580$56e75080$@nexbridge.com/#r in the mail archive.
Sincerely,
Randall
-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
next prev parent reply other threads:[~2020-07-17 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 20:24 [ANNOUNCE] Git v2.28.0-rc1 Junio C Hamano
2020-07-17 21:21 ` Randall S. Becker [this message]
2020-07-18 9:48 ` [PATCH] t3200: don't grep for `strerror()` string Martin Ågren
2020-07-18 17:59 ` Junio C Hamano
2020-07-18 20:07 ` Martin Ågren
2020-07-19 17:09 ` Randall S. Becker
2020-07-19 17:23 ` 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='00d001d65c80$3519c960$9f4d5c20$@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).