All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: sowmya.indranna@ibm.com
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] vmcp: skip test on non-s390x architectures
Date: Tue, 24 Mar 2026 17:00:00 +0100	[thread overview]
Message-ID: <acK1AIOCm0qpXsat@yuki.lan> (raw)
In-Reply-To: <20260324143332.2200651-1-sowmya.indranna@ibm.com>

Hi!
> The vmcp test is specific to s390x systems and is not supported on
> other architectures such as ppc64le. Currently, the test fails on
> unsupported platforms.
> 
> Add an architecture check to skip execution on non-s390x systems
> by reporting TCONF, avoiding false test failures.
> 
> Signed-off-by: Sowmya Indranna <sowmya.indranna@ibm.com>
> ---
>  testcases/commands/vmcp/vmcp_m.sh | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/testcases/commands/vmcp/vmcp_m.sh b/testcases/commands/vmcp/vmcp_m.sh
> index 3924a6e11..e40dec4bd 100644
> --- a/testcases/commands/vmcp/vmcp_m.sh
> +++ b/testcases/commands/vmcp/vmcp_m.sh
> @@ -15,6 +15,15 @@ TST_CNT=2
>  TST_TESTFUNC=vmcp_main
>  TST_NEEDS_CMDS="vmcp"
>  
> +# Check if running on s390x architecture
> +check_arch()
> +{
> +	local arch=$(uname -m)
> +	if [ "$arch" != "s390x" ]; then
> +		tst_brk TCONF "vmcp test requires s390x architecture, current: $arch"
> +	fi
> +}

The test has TST_NEEDS_CMDS="vmcp" it shouldn't even start unless there
is vmcp installed. And would expect that vmcp is not installed unless we
are on s390x.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-03-24 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 14:33 [LTP] [PATCH] vmcp: skip test on non-s390x architectures sowmya.indranna--- via ltp
2026-03-24 16:00 ` Cyril Hrubis [this message]
2026-03-24 16:05   ` Sowmya Indranna via ltp

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=acK1AIOCm0qpXsat@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=sowmya.indranna@ibm.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 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.