From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: randall.s.becker@rogers.com
Cc: git@vger.kernel.org, 'Junio C Hamano' <gitster@pobox.com>
Subject: Re: [ANNOUNCE] Git v2.24.0-rc1 - Test Summary for NonStop
Date: Mon, 28 Oct 2019 12:48:50 +0100 [thread overview]
Message-ID: <20191028114850.GR4348@szeder.dev> (raw)
In-Reply-To: <021601d58c32$4f632a10$ee297e30$@rogers.com>
On Sat, Oct 26, 2019 at 03:19:37PM -0400, randall.s.becker@rogers.com wrote:
> 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.
> It would be nice to understand why t0500 is failing before we release the
> official build to our community.
Yeah, that would be nice, but I don't know how we could help, if you
don't even tell us which 7 tests failed... The output of the failed
tests could also be quite useful.
It may or may not be conincidental, but there happens to be 7 tests
in t0500 that use 'test-tool progress --total=<N>', which was affected
by an endianness bug that got fixed in 2b6f6ea1bd (test-progress: fix
test failures on big-endian systems, 2019-10-20). It would be
interesting to see whether t0500 failed before that fix as well.
next prev parent reply other threads:[~2019-10-28 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 19:19 [ANNOUNCE] Git v2.24.0-rc1 - Test Summary for NonStop randall.s.becker
2019-10-28 11:48 ` SZEDER Gábor [this message]
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=20191028114850.GR4348@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=randall.s.becker@rogers.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).