Re: chainlint test failing on Linux sparc64

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Date: May 20, 2024, 09:04 UTC
Message-ID: <bdbf99ae4d6e3669b3506a7d4a26730aa9cd0ed4.camel@physik.fu-berlin.de>
In-Reply-To: <054f58c2de4af289008f28b140d4a4c9ab56f084.camel@physik.fu-berlin.de>

Hi,

On Mon, 2024-05-20 at 10:24 +0200, John Paul Adrian Glaubitz wrote:

Show 5 quoted lines

> 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.

Bisecting was successful and has lead me to this commit:

d00113ec3474a1652a73c11695c7e7b5182d80a7 is the first bad commit
commit d00113ec3474a1652a73c11695c7e7b5182d80a7
Author: Eric Sunshine <sunshine@sunshineco.com>
Date:   Thu Sep 1 00:29:46 2022 +0000

    t/Makefile: apply chainlint.pl to existing self-tests
    
    Now that chainlint.pl is functional, take advantage of the existing
    chainlint self-tests to validate its operation. (While at it, stop
    validating chainlint.sed against the self-tests since it will soon be
    retired.)
(...)

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913