From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Johannes Schindelin'" <Johannes.Schindelin@gmx.de>
Cc: <git@vger.kernel.org>
Subject: RE: [BUG] git 2.24.0-rc1 t0500 on NonStop in Jenkins
Date: Mon, 28 Oct 2019 10:15:31 -0400 [thread overview]
Message-ID: <026401d58d9a$2bbe7600$833b6200$@nexbridge.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1910281405000.46@tvgsbejvaqbjf.bet>
On October 28, 2019 9:07 AM, Johannes Schindelin wrote:
> On Thu, 24 Oct 2019, Randall S. Becker wrote:
> > We are running the regression suite (as we always have) in Jenkins and
> > are finding that t0500 is basically a complete failure. I cannot
> > recreate it using bash where we have a real terminal, but without one,
> > the t0500 consistently fails. I wonder whether any other platform is
> > experiencing the same situation.
>
> This says that a test failed, but it lacks the verbose log, so there is
little else
> left to the willing reader than wild guesses that are almost certainly
> completely missing the culprit.
>
> In other words: verbose log, please. That is, the output of the test
script
> when run with `-i -v -x` (or `-i -V -x` in which case you will want to
analyze the
> contents of `t/test-results/t0500-progress-display.out` and if that does
not
> help, paste it into a reply).
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
+ cat
+ 1> in 0< /tmp/sh1811939370.5
+ test-tool progress --total=3 Working hard
+ 0< in 2> stderr
+ show_cr
+ 0< stderr 1> out
+ 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.
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:15 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 [this message]
2019-10-28 14:52 ` SZEDER Gábor
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='026401d58d9a$2bbe7600$833b6200$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).