All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 5/5] runtest/numa: remove move_pages* test cases
Date: Tue, 2 Oct 2018 15:09:28 +0200	[thread overview]
Message-ID: <20181002130928.GH24796@rei> (raw)
In-Reply-To: <1536849882-28897-6-git-send-email-stanislav.kholmanskikh@oracle.com>

Hi!
> since they are already defined in runtest/syscalls.
> 
> Signed-off-by: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
> ---
>  runtest/numa | 12 ------------
>  1 file changed, 12 deletions(-)
> 
> diff --git a/runtest/numa b/runtest/numa
> index 12aedbb..510c353 100644
> --- a/runtest/numa
> +++ b/runtest/numa
> @@ -1,13 +1 @@
>  Numa-testcases numa01.sh
> -move_pages01 move_pages01
> -move_pages02 move_pages02
> -move_pages03 move_pages03
> -move_pages04 move_pages04
> -move_pages05 move_pages05
> -move_pages06 move_pages06
> -move_pages07 move_pages07
> -move_pages08 move_pages08
> -move_pages09 move_pages09
> -move_pages10 move_pages10
> -move_pages11 move_pages11
> -move_pages12 move_pages12

Or we may remove the numa runtest file from the default scenario, given
that the move_pages tests are in syscalls and the numa01.sh is known to
be broken there is a little value in keeping it in default scenario.

And once I finish the numa01.sh rewrite, we will get set_mempolicy
syscall tests in syscalls runtest file anyways, so we may keep the numa
to be a separate runtest file for a case that someone wants to run only
numa related tests.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2018-10-02 13:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13 14:44 [LTP] [RFC] Unique test case ids in runtest files ? Stanislav Kholmanskikh
2018-09-13 14:44 ` [LTP] [RFC PATCH 1/5] Remove the pipes runtest file Stanislav Kholmanskikh
2018-10-02 13:12   ` Cyril Hrubis
2018-09-13 14:44 ` [LTP] [RFC PATCH 2/5] runtest/syscalls: rename CVE test cases Stanislav Kholmanskikh
2018-10-02 12:53   ` Cyril Hrubis
2018-10-02 16:19     ` Stanislav Kholmanskikh
2018-10-08  9:52     ` Stanislav Kholmanskikh
2018-10-08 10:16       ` Cyril Hrubis
2018-09-13 14:44 ` [LTP] [RFC PATCH 3/5] runtest/sched: removed sched_{set, get}attr " Stanislav Kholmanskikh
2018-10-02 12:55   ` Cyril Hrubis
2018-09-13 14:44 ` [LTP] [RFC PATCH 4/5] runtest/commands: adjust names for keyctl01, sysctl01, unshare01 Stanislav Kholmanskikh
2018-10-02 13:03   ` Cyril Hrubis
2018-10-02 16:21     ` Stanislav Kholmanskikh
2018-10-03  7:42       ` Cyril Hrubis
2018-10-08  9:01         ` Stanislav Kholmanskikh
2018-10-08  9:02           ` Cyril Hrubis
2018-09-13 14:44 ` [LTP] [RFC PATCH 5/5] runtest/numa: remove move_pages* test cases Stanislav Kholmanskikh
2018-10-02 13:09   ` Cyril Hrubis [this message]
2018-10-02 16:25     ` Stanislav Kholmanskikh
2018-10-02 12:51 ` [LTP] [RFC] Unique test case ids in runtest files ? Cyril Hrubis

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=20181002130928.GH24796@rei \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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.