public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: "Nina Schoetterl-Glausch" <nsg@linux.ibm.com>,
	"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
	"Nico Böhr" <nrb@linux.ibm.com>
Cc: David Hildenbrand <david@redhat.com>,
	Thomas Huth <thuth@redhat.com>,
	linux-s390@vger.kernel.org, kvm@vger.kernel.org,
	Andrew Jones <andrew.jones@linux.dev>,
	Colton Lewis <coltonlewis@google.com>,
	Nikos Nikoleris <nikos.nikoleris@arm.com>,
	Sean Christopherson <seanjc@google.com>,
	Shaoqin Huang <shahuang@redhat.com>
Subject: Re: [kvm-unit-tests PATCH 4/9] s390x: topology: Don't use non unique message
Date: Wed, 11 Oct 2023 13:11:03 +0200	[thread overview]
Message-ID: <b62f5ba4-1587-4587-a223-22242727d244@linux.ibm.com> (raw)
In-Reply-To: <20231011085635.1996346-5-nsg@linux.ibm.com>

On 10/11/23 10:56, Nina Schoetterl-Glausch wrote:
> When we test something, i.e. do a report() we want unique messages,
> otherwise, from the test output, it will appear as if the same test was
> run multiple times, possible with different PASS/FAIL values.
> 
> Convert some reports that don't actually test anything topology specific
> into asserts.
> Refine the report message for others.
> 
> Signed-off-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>

Please change to:
s390x: topology: make report messages unique

Reviewed-by: Janosch Frank <frankja@linux.ibm.com>

> ---
>   s390x/topology.c | 12 ++++++------
>   1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/s390x/topology.c b/s390x/topology.c
> index 49d6dfeb..5374582f 100644
> --- a/s390x/topology.c
> +++ b/s390x/topology.c
> @@ -114,7 +114,7 @@ static void check_polarization_change(void)
>   	report_prefix_push("Polarization change");
>   
>   	/* We expect a clean state through reset */
> -	report(diag308_load_reset(1), "load normal reset done");
> +	assert(diag308_load_reset(1));
>   
>   	/*
>   	 * Set vertical polarization to verify that RESET sets
> @@ -123,7 +123,7 @@ static void check_polarization_change(void)
>   	cc = ptf(PTF_REQ_VERTICAL, &rc);
>   	report(cc == 0, "Set vertical polarization.");
>   
> -	report(diag308_load_reset(1), "load normal reset done");
> +	assert(diag308_load_reset(1));
>   
>   	cc = ptf(PTF_CHECK, &rc);
>   	report(cc == 0, "Reset should clear topology report");
> @@ -137,25 +137,25 @@ static void check_polarization_change(void)
>   	report(cc == 0, "Change to vertical");
>   
>   	cc = ptf(PTF_CHECK, &rc);
> -	report(cc == 1, "Should report");
> +	report(cc == 1, "Should report change after horizontal -> vertical");
>   
>   	cc = ptf(PTF_REQ_VERTICAL, &rc);
>   	report(cc == 2 && rc == PTF_ERR_ALRDY_POLARIZED, "Double change to vertical");
>   
>   	cc = ptf(PTF_CHECK, &rc);
> -	report(cc == 0, "Should not report");
> +	report(cc == 0, "Should not report change after vertical -> vertical");
>   
>   	cc = ptf(PTF_REQ_HORIZONTAL, &rc);
>   	report(cc == 0, "Change to horizontal");
>   
>   	cc = ptf(PTF_CHECK, &rc);
> -	report(cc == 1, "Should Report");
> +	report(cc == 1, "Should report change after vertical -> horizontal");
>   
>   	cc = ptf(PTF_REQ_HORIZONTAL, &rc);
>   	report(cc == 2 && rc == PTF_ERR_ALRDY_POLARIZED, "Double change to horizontal");
>   
>   	cc = ptf(PTF_CHECK, &rc);
> -	report(cc == 0, "Should not report");
> +	report(cc == 0, "Should not report change after horizontal -> horizontal");
>   
>   	report_prefix_pop();
>   }


  reply	other threads:[~2023-10-11 11:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11  8:56 [kvm-unit-tests PATCH 0/9] s390x: topology: Fixes and extension Nina Schoetterl-Glausch
2023-10-11  8:56 ` [kvm-unit-tests PATCH 1/9] s390x: topology: Fix report message Nina Schoetterl-Glausch
2023-10-11 10:56   ` Janosch Frank
2023-10-11 11:10     ` Nina Schoetterl-Glausch
2023-10-11 11:30       ` Janosch Frank
2023-10-11 11:41         ` Nina Schoetterl-Glausch
2023-10-11 13:36   ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 2/9] s390x: topology: Use parameter in stsi_get_sysib Nina Schoetterl-Glausch
2023-10-11 11:05   ` Janosch Frank
2023-10-12 14:44   ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 3/9] s390x: topology: Fix parsing loop Nina Schoetterl-Glausch
2023-10-11 11:07   ` Janosch Frank
2023-10-11 11:16     ` Nina Schoetterl-Glausch
2023-10-12 14:46   ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 4/9] s390x: topology: Don't use non unique message Nina Schoetterl-Glausch
2023-10-11 11:11   ` Janosch Frank [this message]
2023-10-13  8:16   ` Nico Boehr
2023-10-13  9:18     ` Nina Schoetterl-Glausch
2023-10-11  8:56 ` [kvm-unit-tests PATCH 5/9] s390x: topology: Refine stsi header test Nina Schoetterl-Glausch
2023-10-11 11:16   ` Janosch Frank
2023-10-11 11:19     ` Nina Schoetterl-Glausch
2023-10-11 11:22       ` Janosch Frank
2023-10-17 12:31         ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 6/9] s390x: topology: Rename topology_core to topology_cpu Nina Schoetterl-Glausch
2023-10-11 11:31   ` Janosch Frank
2023-10-17 12:32   ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 7/9] s390x: topology: Rewrite topology list test Nina Schoetterl-Glausch
2023-10-17 13:29   ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 9/9] s390x: topology: Add complex topology test Nina Schoetterl-Glausch
2023-10-19 10:58   ` Nico Boehr

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=b62f5ba4-1587-4587-a223-22242727d244@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=andrew.jones@linux.dev \
    --cc=coltonlewis@google.com \
    --cc=david@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nikos.nikoleris@arm.com \
    --cc=nrb@linux.ibm.com \
    --cc=nsg@linux.ibm.com \
    --cc=seanjc@google.com \
    --cc=shahuang@redhat.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