public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH] testsuite: Improve SSH ping
Date: Fri, 17 Mar 2023 05:11:30 +0100	[thread overview]
Message-ID: <20230317041130.7987-1-ubely@ilbers.de> (raw)

When qemu machine boots, it may happen that consecutive SSH connection
fails right after the previous good one. So, we get a situation when
the command/script fails after we consider SSH is ready.

This patch improves detection of SSH server ready status by making at
least three good consecutive SSH pings.

Example of debug output that shows the case:

```
| Waiting for SSH server ready...
| SSH ping result: 255, left: 300s # <== machine is booting
| SSH ping result: 255, left: 294s
| SSH ping result: 255, left: 288s
| SSH ping result: 255, left: 282s
| SSH ping result: 255, left: 276s
| SSH ping result: 255, left: 270s
| SSH ping result: 255, left: 264s
| SSH ping result: 255, left: 258s
| SSH ping result: 0, left: 253s   # <== SSH server is up...
| SSH ping result: 0, left: 251s
| SSH ping result: 255, left: 250s # <== but one ping failed again
| SSH ping result: 0, left: 248s
| SSH ping result: 0, left: 245s
| SSH ping result: 0, left: 243s
| SSH server is ready
| `lsmod | grep example_module` returned 0
```

Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
 testsuite/cibuilder.py | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/testsuite/cibuilder.py b/testsuite/cibuilder.py
index 9e84c3a3..4e568b8e 100755
--- a/testsuite/cibuilder.py
+++ b/testsuite/cibuilder.py
@@ -257,17 +257,25 @@ class CIBuilder(Test):
         self.log.debug('Waiting for SSH server ready...')
 
         rc = None
+        goodcnt = 0
         while time.time() < timeout:
             if proc.poll() is not None:
                 self.log.error('Machine is not running')
                 return rc
 
             rc = self.exec_cmd('/bin/true', cmd_prefix)
+            time_left = timeout - time.time()
+            self.log.debug('SSH ping result: %d, left: %.fs' % (rc, time_left))
             time.sleep(1)
 
             if rc == 0:
-                self.log.debug('SSH server is ready')
-                break
+                goodcnt += 1
+                # Let 3 good SSH pings to make sure SSH connection is stable
+                if goodcnt >= 3:
+                    self.log.debug('SSH server is ready')
+                    break
+            else:
+                goodcnt = 0
 
         if rc != 0:
             self.log.error('SSH server is not ready')
-- 
2.20.1


             reply	other threads:[~2023-03-17  4:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  4:11 Uladzimir Bely [this message]
2023-03-17  8:17 ` Henning Schild
2023-03-17  8:53 ` Henning Schild
2023-03-20  8:51   ` Uladzimir Bely
2023-03-20  9:12     ` Henning Schild
2023-03-20  9:17       ` Uladzimir Bely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230317041130.7987-1-ubely@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox