U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Heiko Schocher <hs@nabladev.com>, Heiko Schocher <hs@denx.de>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Love Kumar <love.kumar@amd.com>, Simon Glass <sjg@chromium.org>,
	Tom Rini <trini@konsulko.com>
Subject: [PATCH v1 5/8] test: increase timeouts
Date: Sat,  5 Apr 2025 20:46:23 +0200	[thread overview]
Message-ID: <20250405184626.22377-6-hs@denx.de> (raw)
In-Reply-To: <20250405184626.22377-1-hs@denx.de>

From: Heiko Schocher <hs@nabladev.com>

running tests on github/gitlab while board is somewhere in
the wide world, needs bigger command and standard timeouts.

Increase them to:

TIMEOUT_MS = 60000                  # Standard timeout
TIMEOUT_CMD_MS = 45000              # Command-echo timeout

Signed-off-by: Heiko Schocher <hs@nabladev.com>
Signed-off-by: Heiko Schocher <hs@denx.de>
---

 test/py/u_boot_console_base.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/test/py/u_boot_console_base.py b/test/py/u_boot_console_base.py
index 7eaceb39d9..0aabedc394 100644
--- a/test/py/u_boot_console_base.py
+++ b/test/py/u_boot_console_base.py
@@ -30,8 +30,8 @@ PAT_ID = 0
 PAT_RE = 1
 
 # Timeout before expecting the console to be ready (in milliseconds)
-TIMEOUT_MS = 30000                  # Standard timeout
-TIMEOUT_CMD_MS = 10000              # Command-echo timeout
+TIMEOUT_MS = 60000                  # Standard timeout
+TIMEOUT_CMD_MS = 45000              # Command-echo timeout
 
 # Timeout for board preparation in lab mode. This needs to be enough to build
 # U-Boot, write it to the board and then boot the board. Since this process is
-- 
2.20.1


  parent reply	other threads:[~2025-04-05 18:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-05 18:46 [PATCH v1 0/8] This series introduces U-Boot tests with tbot on real hardware Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 1/8] test/py/requirements.txt: update coverage Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 2/8] tools/buildman/requirements.txt: " Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 3/8] test/py/requirements.txt: increase filelock version Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 4/8] test/py/requirements.txt: remove unittest2 and testtools Heiko Schocher
2025-04-05 18:46 ` Heiko Schocher [this message]
2025-04-05 18:46 ` [PATCH v1 6/8] [RFC] CI: add U-Boot testing on real HW with tbot Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 7/8] .gitlab-ci.yml: add tbot-lab Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 8/8] scripts: add helper for getting infos from your patchwork ToDo list Heiko Schocher

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=20250405184626.22377-6-hs@denx.de \
    --to=hs@denx.de \
    --cc=hs@nabladev.com \
    --cc=love.kumar@amd.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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