From: <randall.s.becker@rogers.com>
To: <git@vger.kernel.org>
Cc: "'Junio C Hamano'" <gitster@pobox.com>
Subject: Re: [ANNOUNCE] Git v2.24.0-rc1 - Test Summary for NonStop
Date: Sat, 26 Oct 2019 15:19:37 -0400 [thread overview]
Message-ID: <021601d58c32$4f632a10$ee297e30$@rogers.com> (raw)
This is the test summary for the HPE NonStop TNS/E platform for git
2.24.0-rc1. All tests passed except as follows:
[NEW] 1. t0500-progress-display - failed 7 out of 11. This appears to
consistently fail when run under Jenkins but consistently succeeds when run
from a non-disconnected real terminal. The difference from a pipe handling
standpoint with Jenkins is that it provides a stdout opened using O_WRONLY
rather than O_RDWR or other open() modes that might exist - we have seen
problems resulting from differences between process initiation under Jenkins
and connected terminals in other products. This failure was not present in
2.23.0.
2. t9001-send-email - obvious failure because there is no working sendmail
on the platform. This is an expected failure, so no issue.
3. t9020-remote-svn - there is no svn on platform, but the test detection
does not deal with this. This is an expected failure, so again, no issue.
It would be nice to understand why t0500 is failing before we release the
official build to our community.
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-10-26 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 19:19 randall.s.becker [this message]
2019-10-28 11:48 ` [ANNOUNCE] Git v2.24.0-rc1 - Test Summary for NonStop SZEDER Gábor
2019-10-28 14:17 ` 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='021601d58c32$4f632a10$ee297e30$@rogers.com' \
--to=randall.s.becker@rogers.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).