GNU bug report logs - #44712
Inconsistent directory lookup of executable in dejagnu.exp/host_execute

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 44712 in the body.
You can then email your comments to 44712 AT debbugs.gnu.org in the normal way.

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

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

From: Robert Menteer <reetnem <at> mac.com>
To: Robert Menteer via Bug-dejagnu <bug-dejagnu <at> gnu.org>
Subject: Inconsistent directory lookup of executable in
 dejagnu.exp/host_execute
Date: Tue, 17 Nov 2020 14:15:25 -0500

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

If you call ‘host_execute /fullpath/testsuite/unit-test/unit’, host_execute can find the unit test but not execute it.

If you call ‘host_execute /testsuite/unit-test/unit’, host_execute can’t find the unit test (but could execute it).

If you call ‘host_execute testsuite/unit-test/unit’, host_execute works.

This is because the lookup of the executable is done using:

if {![file exists ${executable}]} 

And the executing is done using:

spawn -noecho "./$executable" ${params}

Please make the usage of $executable consistent and document how host_execute should be called.

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

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

From: Jacob Bachmeyer <jcb62281 <at> gmail.com>
To: Robert Menteer <reetnem <at> mac.com>, 
 Robert Menteer via Bug-dejagnu <bug-dejagnu <at> gnu.org>
Cc: 44712-done <at> debbugs.gnu.org
Subject: Re: bug#44712: Inconsistent directory lookup of executable in
 dejagnu.exp/host_execute
Date: Tue, 17 Nov 2020 21:58:08 -0600

Robert Menteer via Bug-dejagnu via wrote:
> This is because the lookup of the executable is done using:
>
> if {![file exists ${executable}]} 
>
> And the executing is done using:
>
> spawn -noecho "*_./_*$executable" ${params}
>
> Please make the usage of $executable consistent and document how 
> host_execute should be called.

The code you are complaining about was fixed in commit 
89f58b27832f8fc7b443988d02e56cfaba12eb5a as part of support for 
regression testing for bug#42399 and documentation for host_execute was 
added in the node "Running unit tests" in commit 
aa173cea24b94d3f714f07bbbfda85740e8e77db.  These will be in 1.6.3.

Closing report as already fixed; not in current master.


-- Jacob

Previous Next

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