GNU bug report logs - #79077
host_execute and non-zero exit status

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: jcb62281 <at> gmail.com
Cc: tracker <at> debbugs.gnu.org
Subject: bug#79077: closed (host_execute and non-zero exit status)
Date: Sat, 26 Jul 2025 04:22:02 +0000

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

Your message dated Fri, 25 Jul 2025 23:21:19 -0500
with message-id <3aaa197b-b33a-4d0b-be49-45c920c97b87 <at> gmail.com>
and subject line Re: bug#79077: host_execute and non-zero exit status
has caused the debbugs.gnu.org bug report #79077,
regarding host_execute and non-zero exit status
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
79077: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=79077
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Marc Nieper-Wißkirchen <marc.nieper+gnu <at> gmail.com>
To: bug-dejagnu <at> gnu.org
Subject: host_execute and non-zero exit status
Date: Wed, 23 Jul 2025 09:31:21 +0200

Hi,

The host_execute procedure in dejagnu.exp (see [1]) doesn't seem to
check the exit status of the executed test programs. A test program
that simply aborts (e.g. using the C function of the same name) won't
cause any testsuite failures. This seems brittle and like a
misfeature.

What is the supposed way to deal with this?

Thanks,

Marc

--

[1] https://www.gnu.org/software/dejagnu/manual/Running-unit-tests.html

[Message part 3 (message/rfc822, inline)]

From: Jacob Bachmeyer <jcb62281 <at> gmail.com>
To: Marc Nieper-Wißkirchen <marc.nieper+gnu <at> gmail.com>
Cc: 79077-done <at> debbugs.gnu.org
Subject: Re: bug#79077: host_execute and non-zero exit status
Date: Fri, 25 Jul 2025 23:21:19 -0500

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

On 7/25/25 06:30, Marc Nieper-Wißkirchen wrote:
> Hi,
>
> Am Fr., 25. Juli 2025 um 04:14 Uhr schrieb Jacob Bachmeyer<jcb62281 <at> gmail.com>:
>
> [...]
>
>> Am Do., 24. Juli 2025 um 05:09 Uhr schrieb Jacob Bachmeyer<jcb62281 <at> gmail.com>:
>>
>> On 7/23/25 02:31, Marc Nieper-Wißkirchen wrote:
>> [...]
>>
>> [...]  DejaGnu generally supports running tests on "remote" target boards and a target connected over a serial line is unlikely to return an exit code.  The only way to be sure that a dependency on the exit code will not creep in is to ignore the exit code.
> With the recent addition of the "END" token, this is probably moot;
> without, how would have DejaGnu handled a test running remotely, say
> over a serial line, where the connection drops early? I saw a non-zero
> exit code as an analogue of such a dropped connection, which could be
> expressed by an "UNRESOLVED" result.

Previously, DejaGnu gave no indication that anything was wrong if a unit 
test program failed to complete, although older versions used a "Totals" 
line as an implicit end marker.  This was changed when the unit testing 
protocol was documented to avoid possible misfires if a unit test 
happens to emit a line beginning with "Totals"; the new "END" marker 
uses a syntax that is explicitly documented as reserved for unit test 
messages to the framework.

>> [...]
>>
>> An initial solution has been pushed to Savannah on the PR79077 branch. DejaGnu can now be run directly from a Git checkout, you should be able to simply pass RUNTEST=/full/name/of/working/tree/runtest on the "make check" command line.
> That is great news. Thank you! Moreover, thank you very much for your
> ideas about the Valgrind mapper; very helpful, indeed.

You are welcome.

Since an improvement has been merged to Git master, this closes the bug 
report.


-- Jacob

[Message part 5 (text/html, inline)]

Previous Next

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