From: Yixin Zhang <yixin.zhang@intel.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH ltp 4/5] runtest/crashme: rename mem01 to avoid duplication
Date: Fri, 9 Aug 2019 14:19:59 +0800 [thread overview]
Message-ID: <20190809062000.8671-4-yixin.zhang@intel.com> (raw)
In-Reply-To: <20190809062000.8671-1-yixin.zhang@intel.com>
mem01 is already in runtest file mm. Rename the test to mem01_crashme
here.
Signed-off-by: Yixin Zhang <yixin.zhang@intel.com>
---
runtest/crashme | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/runtest/crashme b/runtest/crashme
index a4c5b41cc..e853663e6 100644
--- a/runtest/crashme
+++ b/runtest/crashme
@@ -10,7 +10,7 @@ crash01 crash01
crash02 crash02
# Generate random syscalls and execute them, less probability
# to hose your system, but still.
-mem01 mem01 -r
+mem01_crashme mem01 -r
# Memory eater. Loves to be run in parallel with other programs.
# May panic on buggy systems if the OOM killer was not fast enough :-)
fork12 fork12
--
2.17.1
next prev parent reply other threads:[~2019-08-09 6:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 6:19 [LTP] [PATCH ltp 1/5] runtest/scsi_debug.part1: remove duplicated test for reiserfs filesystem Yixin Zhang
2019-08-09 6:19 ` [LTP] [PATCH ltp 2/5] runtest: rename gf*** and rwtest{1..5} in lvm.part{1, 2} and scsi_debug.part1 Yixin Zhang
2019-08-09 14:13 ` Cyril Hrubis
2019-09-02 9:00 ` Petr Vorel
2019-08-09 6:19 ` [LTP] [PATCH ltp 3/5] runtest/ltp-aiodio.part4: rename aiodio_append tests to avoid duplication Yixin Zhang
2019-09-02 9:16 ` Petr Vorel
2019-08-09 6:19 ` Yixin Zhang [this message]
2019-08-30 13:14 ` [LTP] [PATCH ltp 4/5] runtest/crashme: rename mem01 " Petr Vorel
2019-09-02 1:39 ` Zhang, Yixin
2019-08-09 6:20 ` [LTP] [PATCH ltp 5/5] runtest/numa: rename duplicated test cases Yixin Zhang
2019-08-09 13:43 ` Cyril Hrubis
2019-08-09 13:58 ` [LTP] [PATCH ltp 1/5] runtest/scsi_debug.part1: remove duplicated test for reiserfs filesystem 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=20190809062000.8671-4-yixin.zhang@intel.com \
--to=yixin.zhang@intel.com \
--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