Re: [ANNOUNCE] Git v2.24.0-rc1 - Test Summary for NonStop

Re: [ANNOUNCE] Git v2.24.0-rc1 - Test Summary for NonStop

[randall.s.becker]

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.

Re: [ANNOUNCE] Git v2.24.0-rc1 - Test Summary for NonStop

[SZEDER Gábor]

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.

RE: [ANNOUNCE] Git v2.24.0-rc1 - Test Summary for NonStop

[Randall S. Becker]

On October 28, 2019 7:49 AM, SZEDER Gábor wrote:
> On Sat, Oct 26, 2019 at 03:19:37PM -0400, randall.s.becker@rogers.com
> wrote:
> 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.

Test output provided in a separate thread: https://public-inbox.org/git/026401d58d9a$2bbe7600$833b6200$@nexbridge.com/

Regards,
Randall