From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: chainlint test failing on Linux sparc64
Date: Mon, 20 May 2024 10:24:41 +0200 [thread overview]
Message-ID: <054f58c2de4af289008f28b140d4a4c9ab56f084.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <CAPig+cS+BcQ2t564m8Q4GO+MAThgq8pV0fEFD4S0FBfwokO2Ng@mail.gmail.com>
Hi Eric,
On Mon, 2024-05-20 at 04:21 -0400, Eric Sunshine wrote:
> The thing failing here is chainlint's own self-test, which you don't
> actually need if you're merely building Git. You'd only care about
> chainlint (let alone its self-test) if you're modifying tests or
> creating new ones. You can bypass chainlint altogether by setting
> environment variable GIT_TEST_CHAIN_LINT=0.
>
> That said, chainlint is just a Perl script, and you can manually run
> the self-test like this:
>
> cd t
> make check-chainlint
>
> The output you posted is coming from this line in t/Makefile:
>
> diff -u '$(CHAINLINTTMP_SQ)'/expect '$(CHAINLINTTMP_SQ)'/actual
>
> Based upon what you pasted, it looks like the "actual" file has no
> content. That might suggest a problem with this line which immediately
> precedes it:
>
> $(CHAINLINT) --emit-all '$(CHAINLINTTMP_SQ)'/tests | \
> sed -e 's/^[1-9][0-9]* //' >'$(CHAINLINTTMP_SQ)'/actual && \
>
> "actual" might end up empty if the Perl script isn't emitting anything
> for some reason, or if `sed` isn't emitting anything. Presumably you
> have a working `sed` installed(?), but do you have Perl installed?
Thanks a lot for the elaborate answer!
I think the problem seems to be that the testsuite is not properly invoked
at all. When I run the testsuite with v2.37.7, all tests are run and pass,
but starting with v2.38.0, it only runs the chainlint test and exists.
I am trying to bisect this now.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2024-05-20 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 7:56 chainlint test failing on Linux sparc64 John Paul Adrian Glaubitz
2024-05-20 8:21 ` Eric Sunshine
2024-05-20 8:24 ` John Paul Adrian Glaubitz [this message]
2024-05-20 9:04 ` John Paul Adrian Glaubitz
2024-05-20 9:36 ` Eric Sunshine
2024-05-20 9:56 ` John Paul Adrian Glaubitz
2024-05-20 9:58 ` Eric Sunshine
2024-05-20 10:02 ` John Paul Adrian Glaubitz
2024-05-20 11:02 ` John Paul Adrian Glaubitz
2024-05-20 16:04 ` Junio C Hamano
2024-05-20 16:07 ` John Paul Adrian Glaubitz
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=054f58c2de4af289008f28b140d4a4c9ab56f084.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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.
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).