From: Cui Bixuan <cuibixuan@huawei.com>
To: Alexey Kodanev <alexey.kodanev@oracle.com>
Cc: zhuyanpeng@huawei.com, ltp-list@lists.sourceforge.net,
zhanyongming@huawei.com
Subject: [LTP] [PATCH v2] commands/logrotate:run the case once again will failed
Date: Tue, 7 Jul 2015 17:13:30 +0800 [thread overview]
Message-ID: <559B983A.3090003@huawei.com> (raw)
In-Reply-To: <559A9148.8060200@oracle.com>
Including the rules in /etc/logrotate.d/ will cause the case failed
when run it at the second time.
Signed-off-by: Alexey Kodanev <alexey.kodanev@oracle.com>
Signed-off-by: Cui Bixuan <cuibixuan@huawei.com>
---
testcases/commands/logrotate/logrotate_tests.sh | 4 ----
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/testcases/commands/logrotate/logrotate_tests.sh b/testcases/commands/logrotate/logrotate_tests.sh
index 2a793cc..e845670 100755
--- a/testcases/commands/logrotate/logrotate_tests.sh
+++ b/testcases/commands/logrotate/logrotate_tests.sh
@@ -163,8 +163,6 @@ test01()
compress
# RPM packages drop log rotation information into this directory
- include /etc/logrotate.d
-
/var/log/tst_logfile {
rotate 5
weekly
@@ -201,8 +199,6 @@ test01()
# check if /etc/logrotate.d is included/
# check if 5 rotations are forced.
# check if compression is done.
- grep "including /etc/logrotate.d" $LTPTMP/tst_logrotate.out \
- > $LTPTMP/tst_logrotate.err 2>&1 || RC=$?
grep "reading config file $LTPTMP/tst_logrotate.conf" \
$LTPTMP/tst_logrotate.out > $LTPTMP/tst_logrotate.err 2>&1 || RC=$?
grep "forced from command line (5 rotations)" \
--
1.6.0.2
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2015-07-07 9:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 12:12 [LTP] [PATCH] commands/logrotate:run the case once again will failed Cui Bixuan
[not found] ` <555D8E94.20605@huawei.com>
2015-05-21 9:28 ` s00318865
2015-05-29 1:25 ` Cui Bixuan
2015-05-30 7:01 ` Yuan Sun
2015-06-01 2:46 ` Li Wang
2015-06-01 3:44 ` Yuan Sun
2015-07-01 12:47 ` Cui Bixuan
2015-07-01 14:10 ` Alexey Kodanev
2015-07-02 12:06 ` Cui Bixuan
2015-07-02 14:22 ` Alexey Kodanev
2015-07-04 3:03 ` Cui Bixuan
2015-07-06 14:31 ` Alexey Kodanev
2015-07-07 9:13 ` Cui Bixuan [this message]
2015-07-09 5:59 ` [LTP] [PATCH v2] " Alexey Kodanev
2015-07-13 8:59 ` Cui Bixuan
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=559B983A.3090003@huawei.com \
--to=cuibixuan@huawei.com \
--cc=alexey.kodanev@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=zhanyongming@huawei.com \
--cc=zhuyanpeng@huawei.com \
/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