From: Wang Yong <wangyong2009@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: LTP <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] Fix failure of the utimensat01 test
Date: Tue, 04 Aug 2009 08:44:26 +0800 [thread overview]
Message-ID: <4A77846A.3030203@cn.fujitsu.com> (raw)
In-Reply-To: <364299f40907301224o4007a6bbnadd176f67d87bf2@mail.gmail.com>
Garrett Cooper wrote as:
> On Wed, Jul 29, 2009 at 11:31 PM, Wang Yong<wangyong2009@cn.fujitsu.com> wrote:
>
>> Garrett Cooper wrote as:
>>
>>> On Wed, Jul 29, 2009 at 6:33 PM, Wang Yong<wangyong2009@cn.fujitsu.com>
>>> wrote:
>>>
>>>
>>>> The error handling for "RW" opt of run_test brought about error results.
>>>> This patch fixed that.
>>>>
>>>> Signed-off-by: WangYong <wangyong2009@cn.fujitsu.com>
>>>>
>>>> diff -Nurp a/testcases/kernel/syscalls/utimensat/utimensat_tests.sh
>>>> b/testcases/kernel/syscalls/utimensat/utimensat_tests.sh
>>>> --- a/testcases/kernel/syscalls/utimensat/utimensat_tests.sh
>>>> 2009-07-28 16:23:39.000000000 +0800
>>>> +++ b/testcases/kernel/syscalls/utimensat/utimensat_tests.sh
>>>> 2009-07-28 17:32:26.000000000 +0800
>>>> @@ -260,22 +260,22 @@ echo "Testing read-only file, owned by s
>>>> echo
>>>>
>>>>
>>> [...]
>>>
>>> Don't these changes actually conflict with the testcase's purpose,
>>> given the messages echoed placed directly above the commands?
>>> Thanks,
>>> -Garrett
>>>
>>>
>>>
>> Hi Garrett,
>>
>> This patch doesn't change the testcase's purpose.
>> And the test results prove it.
>>
>
> Wang,
> You're changing everything to RW -- how is that not contradicting
> the phrase `Testing read-only file'?
> Just because things fail doesn't necessarily mean that the entire
> intent is incorrect. Let's make sure not to lose sight of that point
> :).
> Thanks,
> -Garrett
>
>
Hi,
Thanks for your advice.
I did change the testcase's purpose when I changed the "RW" opt.
And I will make patch in accordance with
the principle of not changing the testcase's purpose.
Thanks,
-Wang Yong
>
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-08-04 0:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 1:33 [LTP] [PATCH] Fix failure of the utimensat01 test Wang Yong
2009-07-30 3:19 ` Garrett Cooper
2009-07-30 6:31 ` Wang Yong
2009-07-30 18:29 ` Subrata Modak
2009-07-30 19:24 ` Garrett Cooper
2009-08-04 0:44 ` Wang Yong [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-30 1:00 Wang Yong
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=4A77846A.3030203@cn.fujitsu.com \
--to=wangyong2009@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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