From: <rsbecker@nexbridge.com>
To: "'Taylor Blau'" <me@ttaylorr.com>
Cc: <git@vger.kernel.org>
Subject: RE: [BUG] Re: Git 2.35.0-rc0
Date: Tue, 11 Jan 2022 15:39:02 -0500 [thread overview]
Message-ID: <013e01d8072b$47fbc4a0$d7f34de0$@nexbridge.com> (raw)
In-Reply-To: <Yd3gJ6C3jU7ZZskc@nand.local>
On January 11, 2022 2:53 PM, Taylor Blau wrote:
> On Mon, Jan 10, 2022 at 10:51:39PM -0500, rsbecker@nexbridge.com
> wrote:
> > I now have a different issue:
> >
> > make -C t/ all
> > make[1]: Entering directory '/home/git/git/t'
> > rm -f -r 'test-results'
> > /usr/coreutils/bin/bash: /usr/bin/perl: Argument list too long
> >
> > Is there anyway to move to xargs? I am not sure why /usr/bin/perl is
> > having issues with the build.
>
> Tracing through t/Makefile, I am _pretty_ sure that this Perl invocation comes
> from the test-lint-shell-syntax recipe.
>
> I wonder if something like this would do the trick?
>
> --- 8< ---
>
> diff --git a/t/Makefile b/t/Makefile
> index 46cd5fc527..d959119133 100644
> --- a/t/Makefile
> +++ b/t/Makefile
> @@ -90,7 +90,7 @@ test-lint-executable:
> echo >&2 "non-executable tests:" $$bad; exit 1; }
>
> test-lint-shell-syntax:
> - @'$(PERL_PATH_SQ)' check-non-portable-shell.pl $(T) $(THELPERS)
> $(TPERF)
> + @echo $(T) $(THELPERS) $(TPERF) | xargs '$(PERL_PATH_SQ)'
> +check-non-portable-shell.pl
>
> test-lint-filenames:
> @# We do *not* pass a glob to ls-files but use grep instead, to catch
>
> --- >8 ---
I think we don't need this yet. My CI/CD system is a bit more robust and does not get stuck here.
--Randall
next prev parent reply other threads:[~2022-01-11 20:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 2:20 [BUG] Re: Git 2.35.0-rc0 rsbecker
2022-01-11 2:52 ` Taylor Blau
2022-01-11 2:57 ` rsbecker
2022-01-11 3:00 ` Taylor Blau
2022-01-11 3:03 ` rsbecker
2022-01-11 3:51 ` rsbecker
2022-01-11 12:51 ` rsbecker
2022-01-11 19:53 ` Taylor Blau
2022-01-11 20:39 ` rsbecker [this message]
2022-01-12 19:18 ` Junio C Hamano
2022-01-12 19:21 ` Taylor Blau
2022-01-13 13:21 ` Ævar Arnfjörð Bjarmason
2022-01-13 18:03 ` Junio C Hamano
[not found] <00ef01d80691$82df3380$889d9a80$@nexbridge.com>
2022-01-11 2:25 ` rsbecker
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='013e01d8072b$47fbc4a0$d7f34de0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
/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).