From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, cardoe@cardoe.com,
Michal Orzel <michal.orzel@amd.com>,
victorm.lira@amd.com
Subject: Re: [PATCH] automation: introduce TEST_TIMEOUT_OVERRIDE
Date: Thu, 3 Oct 2024 23:05:46 +0200 [thread overview]
Message-ID: <Zv8HLCxOXxWN1GHx@mail-itl> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2410031319100.1138574@ubuntu-linux-20-04-desktop>
[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]
On Thu, Oct 03, 2024 at 01:22:51PM -0700, Stefano Stabellini wrote:
> TEST_TIME is set as a CI/CD project variable, as it should be, to match
> the capability and speed of the testing infrastructure.
>
> As it turns out, TEST_TIME defined in test.yaml cannot override
> TEST_TIME defined as CI/CD project variable. As a consequence, today the
> TEST_TIME setting in test.yaml for the Xilinx jobs is ignored.
s/TEST_TIME/\0OUT/
>
> Instead, rename TEST_TIMEOUT to TEST_TIMEOUT_OVERRIDE in test.yaml and
> check for TEST_TIMEOUT_OVERRIDE first in console.exp.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@amd.com>
with commit message fixed:
Reviewed-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
> index 8675016b6a..e947736195 100644
> --- a/automation/gitlab-ci/test.yaml
> +++ b/automation/gitlab-ci/test.yaml
> @@ -84,7 +84,7 @@
> variables:
> CONTAINER: ubuntu:xenial-xilinx
> LOGFILE: qemu-smoke-xilinx.log
> - TEST_TIMEOUT: 120
> + TEST_TIMEOUT_OVERRIDE: 120
> artifacts:
> paths:
> - smoke.serial
> @@ -104,7 +104,7 @@
> LOGFILE: xilinx-smoke-x86_64.log
> XEN_CMD_CONSOLE: "console=com2 com2=57600,8n1,0x2F8,4"
> TEST_BOARD: "crater"
> - TEST_TIMEOUT: 1000
> + TEST_TIMEOUT_OVERRIDE: 1000
> artifacts:
> paths:
> - smoke.serial
> diff --git a/automation/scripts/console.exp b/automation/scripts/console.exp
> index f538aa6bd0..310543c33e 100755
> --- a/automation/scripts/console.exp
> +++ b/automation/scripts/console.exp
> @@ -1,6 +1,8 @@
> #!/usr/bin/expect -f
>
> -if {[info exists env(TEST_TIMEOUT)]} {
> +if {[info exists env(TEST_TIMEOUT_OVERRIDE)]} {
> + set timeout $env(TEST_TIMEOUT_OVERRIDE)
> +} elseif {[info exists env(TEST_TIMEOUT)]} {
> set timeout $env(TEST_TIMEOUT)
> } else {
> set timeout 1500
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-10-03 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 20:22 [PATCH] automation: introduce TEST_TIMEOUT_OVERRIDE Stefano Stabellini
2024-10-03 21:05 ` Marek Marczykowski-Górecki [this message]
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=Zv8HLCxOXxWN1GHx@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=cardoe@cardoe.com \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=victorm.lira@amd.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.