git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Martin Ågren" <martin.agren@gmail.com>
To: Sarah Julia Kriesch <sarah.kriesch@opensuse.org>
Cc: git@vger.kernel.org, andreas.stieger@gmx.de,
	Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: git can not be built for s390x since update to git-2.38.0
Date: Tue, 1 Nov 2022 20:05:36 +0100	[thread overview]
Message-ID: <CAN0heSryxTbJXrRs7-aCNb6u9qXJnYjX7++Ji8jd=YeYTJfoaA@mail.gmail.com> (raw)
In-Reply-To: <f1a5f758-d81f-5985-9b5d-2f0dbfaac071@opensuse.org>

Hi Sarah,

On Tue, 1 Nov 2022 at 19:38, Sarah Julia Kriesch
<sarah.kriesch@opensuse.org> wrote:
>
> I am one of the zsystems Maintainers (s390x architecture) at openSUSE
> and git can not be built any more since the update from 2.37.3 to
> 2.38.0, and with 2.38.1 afterwards. We have tried to debug it.
>
> There is no real test error output, but we can identify, that it is
> happening in the test part with check-chainlint.

> [  387s] make[1]: *** [Makefile:83: check-chainlint] Error 1
> [  387s] make[1]: Leaving directory
> '/home/abuild/rpmbuild/BUILD/git-2.38.1/t'
> [  387s] make[1]: *** Waiting for unfinished jobs....
> [  388s] make: *** [Makefile:3075: test] Error 2
> [  388s] error: Bad exit status from /var/tmp/rpm-tmp.ztqAAp (%check)

> How can we fix this issue?

You can disable this feature by setting the GIT_TEST_CHAIN_LINT
environment variable to "0". That should hopefully allow you to run the
tests successfully.

That shouldn't risk you anything, like reduce test coverage or similar.
That the tests are chainlint-ok (roughly speaking, that they are written
the way the Git project likes its tests) has already been established by
many others at this point.

I'm cc-ing the resident chainlint expert.

Martin

  reply	other threads:[~2022-11-01 19:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 18:04 git can not be built for s390x since update to git-2.38.0 Sarah Julia Kriesch
2022-11-01 19:05 ` Martin Ågren [this message]
2022-11-01 19:38   ` Taylor Blau
2022-11-01 19:41   ` Martin Ågren
2022-11-01 22:03     ` Eric Sunshine
2022-11-02 18:49 ` Todd Zullinger
  -- strict thread matches above, loose matches on Subject: below --
2022-11-06 18:32 Sarah Julia Kriesch
2022-11-06 19:15 ` Sarah Julia Kriesch
2022-11-06 20:42   ` Eric Sunshine
2022-11-07  0:42   ` Todd Zullinger
2022-11-22 18:21   ` Eric Sunshine
2022-11-07  0:41 ` Todd Zullinger
     [not found] <4657a19c-89c3-2237-9e6b-db897a492072@opensuse.org>
2022-11-21  5:12 ` Eric Sunshine
2022-11-22 14:35   ` Ævar Arnfjörð Bjarmason
2022-11-22 16:16     ` Eric Sunshine
2022-11-22 22:01       ` Ævar Arnfjörð Bjarmason
2022-11-22 22:20         ` Eric Sunshine

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='CAN0heSryxTbJXrRs7-aCNb6u9qXJnYjX7++Ji8jd=YeYTJfoaA@mail.gmail.com' \
    --to=martin.agren@gmail.com \
    --cc=andreas.stieger@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=sarah.kriesch@opensuse.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.
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).