CI: fix waiting for final test message (again)

The previous attempt has correct diagnosis, but added -notransfer flag
in a wrong place - it should be used in the first (outer) match out of
two, not the second (inner) one.

Fixes: 1e12cbd6af ("CI: fix waiting for final test message")
Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
This commit is contained in:
Marek Marczykowski-Górecki authored and Andrew Cooper committed 2025-04-14 12:16:43 +01:00
1 parent 7610180ff9
commit 79de6507c5
1 file changed
+4 -4
+4 -4
View File
@@ -60,12 +60,12 @@ if {[info exists env(WAKEUP_CMD)]} {
if {[info exists env(LOG_MSG)]} {
expect {
-re "$env(PASSED)" {
expect -notransfer -re "$env(LOG_MSG)"
-notransfer -re "$env(PASSED)" {
expect -re "$env(LOG_MSG)"
exit 0
}
-re "$env(LOG_MSG)" {
expect -notransfer -re "$env(PASSED)"
-notransfer -re "$env(LOG_MSG)" {
expect -re "$env(PASSED)"
exit 0
}
}
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.