From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: 'Johannes Schindelin' <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [BUG] git 2.24.0-rc1 t0500 on NonStop in Jenkins
Date: Mon, 28 Oct 2019 15:52:20 +0100 [thread overview]
Message-ID: <20191028145220.GU4348@szeder.dev> (raw)
In-Reply-To: <026401d58d9a$2bbe7600$833b6200$@nexbridge.com>
On Mon, Oct 28, 2019 at 10:15:31AM -0400, Randall S. Becker wrote:
> Here is the verbose output from subtest 2 that failed. Sorry it took so
> long, we had to arrange a different Jenkins job to test this in isolation.
> Format issue?
>
> Cheers,
> Randall
>
> expecting success of 0500.2 'progress display with total':
> cat >expect <<-\EOF &&
> Working hard: 33% (1/3)<CR>
> Working hard: 66% (2/3)<CR>
> Working hard: 100% (3/3)<CR>
> Working hard: 100% (3/3), done.
> EOF
>
> cat >in <<-\EOF &&
> progress 1
> progress 2
> progress 3
> EOF
> test-tool progress --total=3 "Working hard" <in 2>stderr &&
>
> show_cr <stderr >out &&
> test_i18ncmp expect out
>
> + cat
> + 1> expect 0< /tmp/sh1811939370.4
Wow :)
> + cat
> + 1> in 0< /tmp/sh1811939370.5
> + test-tool progress --total=3 Working hard
> + 0< in 2> stderr
> + show_cr
> + 0< stderr 1> out
Another wow.
This is unrelated to the test failure, but makes me rather curious:
you run the test script with '-x', that's why we see the trace of
commands executed during the test. Interestingly, though, we don't
see any trace of commands executed within any shell function invoked
in the test, i.e. from show_cr above and test_i18ncmp below.
What kind of shell is this?
> + test_i18ncmp expect out
> --- expect 2019-10-28 14:11:40 +0000
> +++ out 2019-10-28 14:11:41 +0000
> @@ -1,4 +1,2 @@
> -Working hard: 33% (1/3)<CR>
> -Working hard: 66% (2/3)<CR>
> -Working hard: 100% (3/3)<CR>
> -Working hard: 100% (3/3), done.
> +Working hard: 0% (1/12884901888)<CR>
> +Working hard: 0% (3/12884901888), done.
Weird, this looks exactly like the big-endian test failure that was
fixed in 2b6f6ea1bd (test-progress: fix test failures on big-endian
systems, 2019-10-20), but that is already in 2.24.0-rc1 (but not yet
in -rc0).
https://public-inbox.org/git/f1ce445e-6954-8e7b-2dca-3a566ce689a5@physik.fu-berlin.de/
Is NonStop big or little-endian? Does t0500 pass without 2b6f6ea1bd?
> error: last command exited with $?=1
> not ok 2 - progress display with total
> #
> # cat >expect <<-\EOF &&
> # Working hard: 33% (1/3)<CR>
> # Working hard: 66% (2/3)<CR>
> # Working hard: 100% (3/3)<CR>
> # Working hard: 100% (3/3), done.
> # EOF
> #
> # cat >in <<-\EOF &&
> # progress 1
> # progress 2
> # progress 3
> # EOF
> # test-tool progress --total=3 "Working hard" <in 2>stderr &&
> #
> # show_cr <stderr >out &&
> # test_i18ncmp expect out
> #
>
next prev parent reply other threads:[~2019-10-28 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 22:01 [BUG] git 2.24.0-rc1 t0500 on NonStop in Jenkins Randall S. Becker
2019-10-28 13:07 ` Johannes Schindelin
2019-10-28 14:15 ` Randall S. Becker
2019-10-28 14:52 ` SZEDER Gábor [this message]
2019-10-28 15:20 ` Randall S. Becker
2019-10-29 10:16 ` SZEDER Gábor
2019-10-29 14:56 ` Randall S. Becker
2019-11-01 19:29 ` 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=20191028145220.GU4348@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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).