public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] torture: Correctly fetch CPUs for kvm-build.sh with all native language
Date: Fri, 2 Apr 2021 00:48:41 +0200	[thread overview]
Message-ID: <20210401224841.GD116405@lothringen> (raw)
In-Reply-To: <20210401223329.GK2696@paulmck-ThinkPad-P72>

On Thu, Apr 01, 2021 at 03:33:29PM -0700, Paul E. McKenney wrote:
> On Thu, Apr 01, 2021 at 11:08:02PM +0200, Frederic Weisbecker wrote:
> How about like this?  I put this only in kvm.sh for the moment, but
> if these keep cropping up I will just hit all the scripts.  ;-)

Sure, works for me!

Thanks.

> 
> 							Thanx, Paul
> 
> ------------------------------------------------------------------------
> 
> commit 4ca332016ed81c15ebb3b744dbfc462281c544b8
> Author: Paul E. McKenney <paulmck@kernel.org>
> Date:   Thu Apr 1 15:26:56 2021 -0700
> 
>     torture:  Set kvm.sh language to English
>     
>     Some of the code invoked directly and indirectly from kvm.sh parses
>     the output of commands.  This parsing assumes English, which can cause
>     failures if the user has set some other language.  In a few cases,
>     there are language-independent commands available, but this is not
>     always the case.  Therefore, as an alternative to polyglot parsing,
>     this commit sets the LANG environment variable to en_US.UTF-8.
>     
>     Reported-by: Frederic Weisbecker <frederic@kernel.org>
>     Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
> 
> diff --git a/tools/testing/selftests/rcutorture/bin/kvm.sh b/tools/testing/selftests/rcutorture/bin/kvm.sh
> index fab3bd9..390bb97 100755
> --- a/tools/testing/selftests/rcutorture/bin/kvm.sh
> +++ b/tools/testing/selftests/rcutorture/bin/kvm.sh
> @@ -20,6 +20,9 @@ mkdir $T
>  
>  cd `dirname $scriptname`/../../../../../
>  
> +# This script knows only English.
> +LANG=en_US.UTF-8; export LANG
> +
>  dur=$((30*60))
>  dryrun=""
>  KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM

  reply	other threads:[~2021-04-01 22:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 13:26 [PATCH] torture: Correctly fetch CPUs for kvm-build.sh with all native language Frederic Weisbecker
2021-04-01 18:51 ` Paul E. McKenney
2021-04-01 20:31   ` Frederic Weisbecker
2021-04-01 20:40     ` Paul E. McKenney
2021-04-01 20:41       ` Frederic Weisbecker
2021-04-01 21:02         ` Paul E. McKenney
2021-04-01 21:08           ` Frederic Weisbecker
2021-04-01 22:33             ` Paul E. McKenney
2021-04-01 22:48               ` Frederic Weisbecker [this message]
2021-04-05 14:23               ` Christian Kujau
2021-04-05 15:25                 ` Paul E. McKenney

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=20210401224841.GD116405@lothringen \
    --to=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox