From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Torsten Bögershausen'" <tboegi@web.de>,
"'Johannes Schindelin'" <Johannes.Schindelin@gmx.de>
Cc: "'SZEDER Gábor'" <szeder.dev@gmail.com>,
"'Jeff King'" <peff@peff.net>,
git@vger.kernel.org
Subject: RE: t0025 flakey?
Date: Wed, 6 Feb 2019 13:00:43 -0500 [thread overview]
Message-ID: <005501d4be45$e4121c40$ac3654c0$@nexbridge.com> (raw)
In-Reply-To: <20190206171517.s5lskawpdodc74ui@tb-raspi4>
On February 6, 2019 12:15, Torsten Bögershausen wrote:
> To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
> Cc: SZEDER Gábor <szeder.dev@gmail.com>; Jeff King <peff@peff.net>;
> git@vger.kernel.org
> Subject: Re: t0025 flakey?
>
> On Wed, Feb 06, 2019 at 02:52:53PM +0100, Johannes Schindelin wrote:
> > Hi Gábor,
> >
> > On Wed, 6 Feb 2019, SZEDER Gábor wrote:
> >
> > > On Wed, Feb 06, 2019 at 11:25:38AM +0100, Johannes Schindelin wrote:
> > >
> > > > at first I thought that those intermittent test failures were
> > > > limited to Windows, but they are not: I can see it now in a build
> > > > on 32-bit Linux.
> > > > Full logs here:
> > > >
> > > > https://dev.azure.com/gitgitgadget/git/_build/results?buildId=1032
> > > > &_a=summary&view=ms.vss-test-web.build-test-results-tab
> > > >
> > > > Excerpt from the failing test case:
> > > >
> > > > -- snip --
> > > > not ok 2 - renormalize CRLF in repo expecting success:
> > > > echo "*.txt text=auto" >.gitattributes &&
> > > > git add --renormalize "*.txt" &&
> > > > cat >expect <<-\EOF &&
> > > > i/lf w/crlf attr/text=auto CRLF.txt
> > > > i/lf w/lf attr/text=auto LF.txt
> > > > i/lf w/mixed attr/text=auto CRLF_mix_LF.txt
> > > > EOF
> > > > git ls-files --eol |
> > > > sed -e "s/ / /g" -e "s/ */ /g" |
> > > > sort >actual &&
> > > > test_cmp expect actual
> > > >
> > > > + echo *.txt text=auto
> > > > + git add --renormalize *.txt
> > > > + cat
> > > > + sort
> > > > + sed -e s/ / /g -e s/ */ /g
> > > > + git ls-files --eol
> > > > + test_cmp expect actual
> > > > + diff -u expect actual
> > > > --- expect 2019-02-06 09:39:42.080733629 +0000
> > > > +++ actual 2019-02-06 09:39:42.088733629 +0000
> > > > @@ -1,3 +1,3 @@
> > > > -i/lf w/crlf attr/text=auto CRLF.txt
> > > > +i/crlf w/crlf attr/text=auto CRLF.txt
> > > > i/lf w/lf attr/text=auto LF.txt
> > > > -i/lf w/mixed attr/text=auto CRLF_mix_LF.txt
> > > > +i/mixed w/mixed attr/text=auto CRLF_mix_LF.txt
> > > > error: last command exited with $?=1
> > > > -- snap --
> > > >
> > > > Any ideas?
> > >
> > > I reported this and Peff looked into it on the way to Git Merge, but
> > > not working solution yet.
> > >
> > > https://public-inbox.org/git/20190129225121.GD1895@sigill.intra.peff
> > > .net/T/#u
> >
> > Thank you!
> > Dscho
>
> I shortly looked into the pointers here - Is t0025 flaky after the fix
from Peff:
>
> [PATCH] add: use separate ADD_CACHE_RENORMALIZE flag
>
> Or has it always been shaky ?
> Does anybody know ?
The NonStop port has traditionally had issues with t0025, which we tended to
ignore because things did work. We wrote those off as bash issues in t0025
since they seemed to be corrected when we picked up a new bash version about
a year ago. I will keep monitoring this, particularly when 2.21 comes out.
Cheers,
Randall
-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
next prev parent reply other threads:[~2019-02-06 18:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 10:25 t0025 flakey? Johannes Schindelin
2019-02-06 10:42 ` SZEDER Gábor
2019-02-06 13:52 ` Johannes Schindelin
2019-02-06 17:15 ` Torsten Bögershausen
2019-02-06 17:39 ` SZEDER Gábor
2019-02-06 18:00 ` Randall S. Becker [this message]
2019-02-07 16:58 ` Randall S. Becker
2019-02-07 17:39 ` Junio C Hamano
2019-02-07 23:57 ` SZEDER Gábor
2019-02-08 10:21 ` Randall S. Becker
2019-02-07 2:00 ` [PATCH] add_to_index(): convert forgotten HASH_RENORMALIZE check Jeff King
2019-02-07 4:18 ` Torsten Bögershausen
2019-02-07 21:00 ` Jeff King
2019-02-07 13:17 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005501d4be45$e4121c40$ac3654c0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=szeder.dev@gmail.com \
--cc=tboegi@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).