GNU bug report logs - #70934
Document how to debug failing tests

Previous Next

To reply to this bug, email your comments to 70934 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Bruno Haible <bruno <at> clisp.org>
To: bug-libtool <at> gnu.org
Subject: Document how to debug failing tests
Date: Tue, 14 May 2024 13:59:04 +0200

[Message part 1 (text/plain, inline)]

Hi,

While running the libtool test suite in a continuous integration environment,
I saw two test failures. In order to investigate these test failure, I had
to understand how to pass additional options, and which options, to the
testsuite "program". I did not find this information in the HACKING file.
Therefore here is a patch to add it to the HACKING file.

[0001-Document-how-to-debug-failing-tests.patch (text/x-patch, attachment)]

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Bruno Haible <bruno <at> clisp.org>
To: bug-libtool <at> gnu.org
Subject: Re: Document how to debug failing tests
Date: Tue, 14 May 2024 14:13:16 +0200

[Message part 1 (text/plain, inline)]

In fact, the recipe is more relevant for skipped tests (since for failed
tests, tests/testsuite.dir/NNN/ is kept by default, whereas for skipped
tests it is deleted by default).

Here's an update of the proposed patch.

[0001-Document-how-to-debug-failing-or-skipped-tests.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.