From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] Unique test case ids in runtest files ?
Date: Tue, 2 Oct 2018 14:51:17 +0200 [thread overview]
Message-ID: <20181002125117.GD24796@rei> (raw)
In-Reply-To: <1536849882-28897-1-git-send-email-stanislav.kholmanskikh@oracle.com>
Hi!
> I.e. if we run LTP with the default scenario then
> 1) most of the test cases above are executed twice.
This is problem that would be hard to fix. We would have to rethink how
we organize testcases in the runtest files in the long term to
completely avoid situations like this.
> 2) keyctl01, sysctl01, unshare01 are executed twice.
> Each time they actually point to a different binary/command.
This is a bug that has to be fixed.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2018-10-02 12:51 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
2018-10-02 16:25 ` Stanislav Kholmanskikh
2018-10-02 12:51 ` Cyril Hrubis [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=20181002125117.GD24796@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox