emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#44712: closed (Inconsistent directory lookup of executable in dejagn


From: GNU bug Tracking System
Subject: bug#44712: closed (Inconsistent directory lookup of executable in dejagnu.exp/host_execute)
Date: Wed, 18 Nov 2020 03:59:02 +0000

Your message dated Tue, 17 Nov 2020 21:58:08 -0600
with message-id <5FB49BD0.8030806@gmail.com>
and subject line Re: bug#44712: Inconsistent directory lookup of executable in 
dejagnu.exp/host_execute
has caused the debbugs.gnu.org bug report #44712,
regarding Inconsistent directory lookup of executable in 
dejagnu.exp/host_execute
to be marked as done.

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


-- 
44712: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44712
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Inconsistent directory lookup of executable in dejagnu.exp/host_execute Date: Tue, 17 Nov 2020 14:15:25 -0500
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.

--- End Message ---
--- Begin Message --- Subject: Re: bug#44712: Inconsistent directory lookup of executable in dejagnu.exp/host_execute Date: Tue, 17 Nov 2020 21:58:08 -0600 User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.22) Gecko/20090807 MultiZilla/1.8.3.4e SeaMonkey/1.1.17 Mnenhy/0.7.6.0
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


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]