public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
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: Re: [LTP] [PATCH] commands/logrotate:run the case once again will failed
Date: Sat, 4 Jul 2015 11:03:44 +0800	[thread overview]
Message-ID: <55974D10.5050808@huawei.com> (raw)
In-Reply-To: <5595490E.1010509@oracle.com>

On 2015/7/2 22:22, Alexey Kodanev wrote:
> Hi,
> On 07/02/2015 03:06 PM, Cui Bixuan wrote:
>> On 2015/7/1 22:10, Alexey Kodanev wrote:
>>> The test creates only tst_logfile, why it should remove 'messages-*' and other system logs?
>>>
>>> I see that its configuration file includes logrotate.d/, is it really needed by the test?
>>>
>> The tst_logfile of test created is 'messages-*' and the 'messages-*' will cause the case failed,
>> so we should delete it if we want to the case run succeed at the second time.
> 
> OK, the test does the following basic steps:
> 
> a. create tst_logfile, fill it with messages;
> b. ./logrotate
> c. if [ -f tst_logfile.1.gz ] then test passed.
> 
> Therefore, why bother about 'messages-*' and other logs, the test doesn't check if they were rotated/compressed... so, may be, we should remove "include /etc/logrotate.d/" from the test configuration file so that logrotate rotated only "tst_logfile" and nothing else, what do you think?
> 
Hi,
Your method is better than mine (I learned that how to use logrotate command again yesterday and
found that remove messages-* is not a good idea).

We can remove 'include /etc/logrotate.d' and delete 'grep including /etc/logrotate.d $LTPTMP/tst_logrotate.out'
in case to fix it, what do you think?  If ok, I will send a new patch.


In addition, I have a question, Why including the rules in /etc/logrotate.d/ will cause the case failed
when run it at the second time?

Thanks,
Cui Bixuan

> Thanks,
> Alexey
> 
> 
>> And the test creates tst_logfile base on day time. For example, the system time is '2015 Jul 3',
>> then the case will create 'messages-20150703.gz'. So 'rm -r /var/log/*`date '+%Y%m%d'`*' in patch
>> only delete the message file of case created (after running it) and not other system logs.
>>
>> I think, if the logrotate testcase fail when run it the second time,it's a problem of
>> testcase and we should fix it.
> 
> 
> 


------------------------------------------------------------------------------
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

  reply	other threads:[~2015-07-04  3:04 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 [this message]
2015-07-06 14:31           ` Alexey Kodanev
2015-07-07  9:13             ` [LTP] [PATCH v2] " Cui Bixuan
2015-07-09  5:59               ` 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=55974D10.5050808@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