public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jan Kara <jack@suse.cz>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] Make ./new work for non-root user
Date: Fri, 25 May 2018 11:30:34 +1000	[thread overview]
Message-ID: <20180525013034.GD10363@dastard> (raw)
In-Reply-To: <20180524183055.16031-1-jack@suse.cz>

On Thu, May 24, 2018 at 08:30:55PM +0200, Jan Kara wrote:
> Currently 'new' script sources common/config which tries to find mkfs
> and fails if not found (which is likely for non-root user). This is
> inconvenient as development usually does not happen as root. In fact the
> vast majority of setup in common/config and common/rc is not necessary
> for 'new'. Split out the necessary bits into new common/config-base and
> use it in 'new'. Cleanup common/rc and common/config now that it's only
> used from 'check'.
> 
> Signed-off-by: Jan Kara <jack@suse.cz>
....
> --- a/common/rc
> +++ b/common/rc
> @@ -20,18 +20,9 @@
>  #  Mountain View, CA 94043, USA, or: http://www.sgi.com
>  #-----------------------------------------------------------------------
>  
> -BC=$(which bc 2> /dev/null) || BC=
> +. common/config

Doesn't this means we now include common/config in every test setup
routine, even though the environment it sets up is inherited from
the check function.

If so, that's going to add significantly to the individual test
startup time (which already takes a significant fraction of a
second) and this happens hundreds of times over an auto run instead
of only once when we start the test run. It seems wrong to be doing
this over and over again unecessarily....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2018-05-25  1:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 18:30 [PATCH] Make ./new work for non-root user Jan Kara
2018-05-25  1:30 ` Dave Chinner [this message]
2018-05-28  9:37   ` Jan Kara
2018-05-29  1:16     ` Dave Chinner
2018-05-29  1:39 ` Dave Chinner
2018-05-29  2:01   ` Dave Chinner
2018-05-29 16:36   ` Jan Kara

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=20180525013034.GD10363@dastard \
    --to=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=jack@suse.cz \
    /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