git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Jeff King" <peff@peff.net>,
	"Torsten Bögershausen" <tboegi@web.de>,
	git@vger.kernel.org
Subject: Re: t0025 flakey?
Date: Wed, 6 Feb 2019 11:42:43 +0100	[thread overview]
Message-ID: <20190206104243.GJ10587@szeder.dev> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1902061123410.41@tvgsbejvaqbjf.bet>

On Wed, Feb 06, 2019 at 11:25:38AM +0100, Johannes Schindelin wrote:
> Hi Torsten,
> 
> 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


  reply	other threads:[~2019-02-06 10:42 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 [this message]
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
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=20190206104243.GJ10587@szeder.dev \
    --to=szeder.dev@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --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).