[xen staging] automation/console.exp: do not assume expect is always at /usr/bin/

[patchbot@xxxxxxx]

commit c6867d134eeb3aefcecf022f4ab20c325701ef30
Author:     Roger Pau Monne <roger.pau@xxxxxxxxxx>
AuthorDate: Mon Mar 17 10:31:07 2025 +0100
Commit:     Roger Pau Monne <roger.pau@xxxxxxxxxx>
CommitDate: Thu Mar 20 12:28:30 2025 +0100

    automation/console.exp: do not assume expect is always at /usr/bin/
    
    Instead use env to find the location of expect.
    
    Additionally do not use the -f flag, as it's only meaningful when passing
    arguments on the command line, which we never do for console.exp.  From the
    expect 5.45.4 man page:
    
    > The -f flag prefaces a file from which to read commands from.  The flag
    > itself is optional as it is only useful when using the #! notation (see
    > above), so  that other arguments may be supplied on the command line.
    
    Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
    Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>
---
 automation/scripts/console.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/automation/scripts/console.exp b/automation/scripts/console.exp
index 310543c33e..31ce97b91b 100755
--- a/automation/scripts/console.exp
+++ b/automation/scripts/console.exp
@@ -1,4 +1,4 @@
-#!/usr/bin/expect -f
+#!/usr/bin/env expect
 
 if {[info exists env(TEST_TIMEOUT_OVERRIDE)]} {
     set timeout $env(TEST_TIMEOUT_OVERRIDE)
--
generated by git-patchbot for /home/xen/git/xen.git#staging