From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] oeqa/runtime/ptest: Improve timeout values
Date: Wed, 4 Mar 2026 18:41:56 +0000 [thread overview]
Message-ID: <20260304184156.2025539-2-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20260304184156.2025539-1-richard.purdie@linuxfoundation.org>
The ptest runner command has timeouts disabled which has the side effect of limiting
the command logging. This can lead to incomplete logs and makes issues harder to debug
since the log buffer is lost if things crash or are interrupted.
Pass in a timeout value of the ptest timeout + 30 so that debugging is improved.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/lib/oeqa/runtime/cases/ptest.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/runtime/cases/ptest.py b/meta/lib/oeqa/runtime/cases/ptest.py
index 2887e136719..57cb050a1d3 100644
--- a/meta/lib/oeqa/runtime/cases/ptest.py
+++ b/meta/lib/oeqa/runtime/cases/ptest.py
@@ -60,7 +60,7 @@ class PtestRunnerTest(OERuntimeTestCase):
if not libdir in ptest_dirs:
ptest_dirs.append(libdir)
ptest_timeout = self.td.get('PTEST_RUNNER_TIMEOUT', '450')
- status, output = self.target.run('ptest-runner -t {} -d \"{}\"'.format(ptest_timeout, ' '.join(ptest_dirs)), 0)
+ status, output = self.target.run('ptest-runner -t {} -d \"{}\"'.format(ptest_timeout, ' '.join(ptest_dirs)), timeout=int(ptest_timeout)+30)
os.makedirs(ptest_log_dir)
with open(ptest_runner_log, 'w') as f:
f.write(output)
next prev parent reply other threads:[~2026-03-04 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 18:41 [PATCH 1/2] oeqa/runtime/ptest: Use a timeout with command, remove disabling Richard Purdie
2026-03-04 18:41 ` Richard Purdie [this message]
2026-03-06 11:47 ` [OE-core] " Mathieu Dubois-Briand
2026-03-06 14:28 ` Mathieu Dubois-Briand
2026-03-07 10:52 ` Richard Purdie
2026-03-10 2:14 ` Anibal Limon
2026-03-10 8:12 ` Richard Purdie
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=20260304184156.2025539-2-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/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