From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Cc: <szeder.dev@gmail.com>, "'Max Kirillov'" <max@max630.net>
Subject: RE: [ANNOUNCE] Git v2.21.0-rc1 (NonStop Results)
Date: Thu, 14 Feb 2019 10:04:56 -0500 [thread overview]
Message-ID: <001501d4c476$a94651d0$fbd2f570$@nexbridge.com> (raw)
On February 13, 2019 22:33, Junio C Hamano wrote:
> A release candidate Git v2.21.0-rc1 is now available for testing at the usual
> places. It is comprised of 464 non-merge commits since v2.20.0, contributed
> by 60 people, 14 of which are new faces.
We are currently running through a full regression of v2.21.0-rc1 on NonStop. It will take about 30 hours, but preliminary results, relative to breakages found in rc0 are:
t1308 is fixed.
t1404 is still broken (explainable) - scraping strerror output mismatches reported error on NonStop for EEXIST
t5318 is fixed.
t5403 is fixed.
t5562 still hangs (blocking) - this breaks our CI pipeline since the test hangs and we have no explanation of whether the hang is in git or the tests.
Cheers,
Randall
-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
next reply other threads:[~2019-02-14 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 15:04 Randall S. Becker [this message]
2019-02-14 19:56 ` [ANNOUNCE] Git v2.21.0-rc1 (NonStop Results) Junio C Hamano
2019-02-14 21:36 ` Johannes Schindelin
2019-02-14 22:25 ` Randall S. Becker
2019-02-15 13:02 ` SZEDER Gábor
2019-02-15 13:49 ` Randall S. Becker
2019-02-15 20:37 ` Max Kirillov
2019-02-15 21:13 ` Randall S. Becker
2019-02-16 8:26 ` Max Kirillov
2019-02-18 20:50 ` [PATCH] t5562: chunked sleep to avoid lost SIGCHILD Max Kirillov
2019-02-18 20:54 ` Randall S. Becker
2019-02-18 20:59 ` Max Kirillov
2019-02-19 18:38 ` Junio C Hamano
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='001501d4c476$a94651d0$fbd2f570$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=max@max630.net \
--cc=szeder.dev@gmail.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).