From: Jeff King <peff@peff.net>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Junio C Hamano <gitster@pobox.com>,
olyatelezhnaya@gmail.com, christian.couder@gmail.com,
Git Mailing List <git@vger.kernel.org>
Subject: Re: t006 broken under Mac OS
Date: Sat, 3 Mar 2018 09:27:47 -0500 [thread overview]
Message-ID: <20180303142747.GA28218@sigill.intra.peff.net> (raw)
In-Reply-To: <f711d7ea-b3a0-82c4-6700-5ec285c91115@web.de>
On Sat, Mar 03, 2018 at 01:52:05PM +0100, Torsten Bögershausen wrote:
> Beside that t1006 has a broken indentation (mixed spaces and TABs at
> the beginning of the line, I get 4 errors here under Mac OS:
>
> not ok 15 - Check %(refname) gives empty output
> not ok 36 - Check %(refname) gives empty output
> not ok 58 - Check %(refname) gives empty output
> not ok 89 - Check %(refname) gives empty output
>
>
> Running with debug and verbose shows that the empty files are not empty.
> The characters in the non-empty file are outside the ASCII range,
> so I copy the stuff in here after running `od -c` on the log file.
> And I don't have a clue, where this stuff comes from - but I get different
> "crap" with each run - seams as if there is a read behind a buffer ?
Yeah, I think the ref_array_item.refname flex-parameter is not valid.
This is the same issue Ramsay mentioned in:
https://public-inbox.org/git/58b2bdcd-d621-fd21-ab4d-6a9478319b19@ramsayjones.plus.com/
Junio, I think it probably makes sense to eject ot/cat-batch-format from
pu for now. That series is on pause for a bit while Olga works on some
other refactoring, and it's causing problems for people who test pu
regularly.
-Peff
next prev parent reply other threads:[~2018-03-03 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 12:52 t006 broken under Mac OS Torsten Bögershausen
2018-03-03 14:27 ` Jeff King [this message]
2018-03-05 21:34 ` Junio C Hamano
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=20180303142747.GA28218@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=olyatelezhnaya@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.
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).