From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Thomas Huth" <thuth@redhat.com>,
kvm@vger.kernel.org, "Nico Böhr" <nrb@linux.ibm.com>
Cc: "Janosch Frank" <frankja@linux.ibm.com>,
<linux-s390@vger.kernel.org>,
"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
"Marc Hartmayer" <mhartmay@linux.ibm.com>
Subject: Re: [kvm-unit-tests PATCH] scripts/s390x: Fix the execution of the PV tests
Date: Tue, 04 Jun 2024 14:50:06 +1000 [thread overview]
Message-ID: <D1QYN902JX0V.2DJE0WMU5DRFK@gmail.com> (raw)
In-Reply-To: <20240603075944.150445-1-thuth@redhat.com>
On Mon Jun 3, 2024 at 5:59 PM AEST, Thomas Huth wrote:
> Commit ccb37496 ("scripts: allow machine option to be specified in
> unittests.cfg") added an additonal parameter (the "machine"), but
> we forgot to add it to the spot that runs the PV test cases, so
> those are currently broken without this fix.
Thanks, this is the one you already found? Looks good to me.
Thanks,
Nick
>
> Fixes: ccb37496 ("scripts: allow machine option to be specified in unittests.cfg")
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> scripts/s390x/func.bash | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/s390x/func.bash b/scripts/s390x/func.bash
> index 6b817727..f04e8e2a 100644
> --- a/scripts/s390x/func.bash
> +++ b/scripts/s390x/func.bash
> @@ -35,5 +35,5 @@ function arch_cmd_s390x()
> print_result 'SKIP' $testname '' 'PVM image was not created'
> return 2
> fi
> - "$cmd" "$testname" "$groups pv" "$smp" "$kernel" "$opts" "$arch" "$check" "$accel" "$timeout"
> + "$cmd" "$testname" "$groups pv" "$smp" "$kernel" "$opts" "$arch" "$machine" "$check" "$accel" "$timeout"
> }
prev parent reply other threads:[~2024-06-04 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 7:59 [kvm-unit-tests PATCH] scripts/s390x: Fix the execution of the PV tests Thomas Huth
2024-06-03 11:05 ` Janosch Frank
2024-06-03 11:56 ` Thomas Huth
2024-06-04 4:50 ` Nicholas Piggin [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=D1QYN902JX0V.2DJE0WMU5DRFK@gmail.com \
--to=npiggin@gmail.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mhartmay@linux.ibm.com \
--cc=nrb@linux.ibm.com \
--cc=thuth@redhat.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