From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <ticotimo@gmail.com>, <docs@lists.yoctoproject.org>
Cc: "Tim Orling" <tim.orling@konsulko.com>
Subject: Re: [docs] [PATCH] ref-manual: document PTEST_RUNNER_TIMEOUT variable
Date: Tue, 03 Mar 2026 11:59:48 +0100 [thread overview]
Message-ID: <DGT3FBURVDJ8.3S9VMOJ2UAY8L@bootlin.com> (raw)
In-Reply-To: <20260227200241.66128-1-tim.orling@konsulko.com>
Hi,
On Fri Feb 27, 2026 at 9:02 PM CET, Tim Orling via lists.yoctoproject.org wrote:
[...]
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 208b5e43d..587f67cc6 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -7793,6 +7793,20 @@ system and gives an overview of their function and contents.
> For more information, see
> the :ref:`ref-classes-ptest-python-pytest` class documentation.
>
> + :term:`PTEST_RUNNER_TIMEOUT`
> + Specifies the timeout in seconds for each ptest suite executed by
> + ``ptest-runner`` during :ref:`ref-classes-testimage` runtime testing.
> + The default value is ``"450"`` (7.5 minutes).
> +
> + This variable is set in the :ref:`ref-classes-testimage` class and can
> + be overridden in image recipes to adjust the timeout for specific
> + images or multiconfig variants. For example, in ``core-image-ptest``::
> +
> + PTEST_RUNNER_TIMEOUT:virtclass-mcextend-python3-cffi = "600"
Could you explain why you're using the :virtclass-mcextend-python3-cffi override
here? Seems like a complicated example for this variable's description, but if
it is needed, we might want to explain it?
Antonin
next prev parent reply other threads:[~2026-03-03 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 20:02 [PATCH] ref-manual: document PTEST_RUNNER_TIMEOUT variable Tim Orling
2026-03-03 10:59 ` Antonin Godard [this message]
2026-03-03 20:17 ` [docs] " Tim Orling
2026-03-04 8:27 ` Antonin Godard
[not found] <18983308FFCB97A7.558139@lists.yoctoproject.org>
2026-02-27 20:10 ` Tim Orling
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=DGT3FBURVDJ8.3S9VMOJ2UAY8L@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=ticotimo@gmail.com \
--cc=tim.orling@konsulko.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