In the rlogin tests, expect to see /bin/sh echoed back after sending

/bin/sh.  If we just look for a shell prompt, we can get out of sync
if the login shell decides to clear the line and redisplay the prompt.
(I see bash redisplaying the prompt in 30-50% of test runs; I don't
know what it's thinking.)

git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@21288 dc483132-0cff-0310-8789-dd5450dbe970

diff --git a/src/tests/dejagnu/krb-root/rlogin.exp b/src/tests/dejagnu/krb-root/rlogin.exp
index bc405646776a94a15fb6e4dbc9f5b1c1b77cc41f..a0e8e4ff54951424ff9b4f20d5626b3aab6a0e30 100644 (file)
--- a/src/tests/dejagnu/krb-root/rlogin.exp
+++ b/src/tests/dejagnu/krb-root/rlogin.exp
@@ -174,6 +174,7 @@ proc rlogin_test { } {
     # prompt.
     set testname "shell"
     send "$BINSH\r"
+    expect "$BINSH"
     expect -re "$SHELL_PROMPT"
 
     set testname "date"
@@ -249,6 +250,7 @@ proc rlogin_test { } {
     # prompt.
     set testname "shell"
     send "$BINSH\r"
+    expect "$BINSH"
     expect -re "$SHELL_PROMPT"
 
     # Make sure the encryption is not destroying the text.