From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Jeff King'" <peff@peff.net>
Cc: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.33.0-rc2 (Build/Test Report)
Date: Mon, 16 Aug 2021 16:43:25 -0400 [thread overview]
Message-ID: <01c501d792df$5fcb24b0$1f616e10$@nexbridge.com> (raw)
In-Reply-To: <YRqwIAL/JgJp+RyI@coredump.intra.peff.net>
On August 16, 2021 2:36 PM, Jeff King wrote:
>To: Randall S. Becker <rsbecker@nexbridge.com>
>Cc: 'Junio C Hamano' <gitster@pobox.com>; git@vger.kernel.org
>Subject: Re: [ANNOUNCE] Git v2.33.0-rc2 (Build/Test Report)
>
>On Mon, Aug 16, 2021 at 02:31:34PM -0400, Randall S. Becker wrote:
>
>> >33 - reject long lines #
>> ># z8=zzzzzzzz &&
>> ># z64=$z8$z8$z8$z8$z8$z8$z8$z8 &&
>> ># z512=$z64$z64$z64$z64$z64$z64$z64$z64 &&
>> ># clean_fake_sendmail &&
>> ># cp $patches longline.patch &&
>> ># cat >>longline.patch <<-EOF &&
>> ># $z512$z512
>> ># not a long line
>> ># $z512$z512
>> ># EOF
>> ># test_must_fail git send-email \
>> ># --from="Example <nobody@example.com>" \
>> ># --to=nobody@example.com \
>> ># --smtp-server="$(pwd)/fake.sendmail" \
>> ># --transfer-encoding=8bit \
>> ># $patches longline.patch \
>> ># 2>actual &&
>> ># cat >expect <<-\EOF &&
>> ># fatal: longline.patch:35 is longer than 998 characters
>> ># warning: no patches were sent
>> ># EOF
>> ># test_cmp expect actual
>> >#
>> >/
>>
>> I should point out that all 6 failures in t9001 have the same characteristic - signal 34.
>
>Oh. Then the notion from my other mail of "if it's die(), then other tests would presumably see similar failures" might be true. ;)
When running
/home/git/git/t/trash directory.t9001-send-email: git send-email --from="Example <nobody@example.com>" --to=nobody@example.com --smtp-server="/home/git/git/t/trash directory.t9001-send-email/fake.sendmail" --transfer-encoding=8bit 0001-Second.patch longline.patch
fatal: longline.patch:35 is longer than 998 characters
warning: no patches were sent
/home/git/git/t/trash directory.t9001-send-email: echo $?
162
So this is strange. Where is perl run? I'd like to catch the completion inside git.
next prev parent reply other threads:[~2021-08-16 20:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 14:22 [ANNOUNCE] Git v2.33.0-rc2 (Build/Test Report) Randall S. Becker
2021-08-13 15:00 ` Junio C Hamano
2021-08-13 16:06 ` Jeff King
2021-08-16 18:08 ` Randall S. Becker
2021-08-16 18:35 ` Jeff King
2021-08-16 18:54 ` Randall S. Becker
2021-08-16 21:55 ` Jeff King
2021-08-16 21:59 ` Jeff King
2021-08-16 18:31 ` Randall S. Becker
2021-08-16 18:36 ` Jeff King
2021-08-16 20:43 ` Randall S. Becker [this message]
2021-08-16 21:02 ` Jeff King
2021-08-16 21:54 ` Randall S. Becker
2021-08-16 22:22 ` Jeff King
2021-08-16 22:29 ` Jeff King
2021-08-17 14:30 ` Randall S. Becker
2021-08-17 14: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
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='01c501d792df$5fcb24b0$1f616e10$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).