From: Timothy Shimmin <tes@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: review: xfstests/192 atime test
Date: Mon, 08 Dec 2008 15:52:08 +1100 [thread overview]
Message-ID: <493CA7F8.9070305@sgi.com> (raw)
In-Reply-To: <491A1709.9020705@sgi.com>
Timothy Shimmin wrote:
> Timothy Shimmin wrote:
>> Dave Chinner wrote:
>>> On Tue, Nov 11, 2008 at 05:11:16PM +1100, Timothy Shimmin wrote:
>>>> Attached simple atime test.
>>>> 192.out and group file would be added appropriately.
>>>> Thanks.
>>>> --Tim
>>>> _supported_fs xfs udf nfs
>>>> _supported_os Linux
>>>> delay=150
>>> 150s sleep? It only needs a few seconds for this test.
>>>
>> Not for me. Passed every time at a few secs,
>> that is why I tried longer as was originally reported.
>>
>>>> time3=`_access_time $testfile | tee -a $seq.full`
>>>>
>>>> delta1=`expr $time2 - $time1`
>>>> delta2=`expr $time3 - $time1`
>>>>
>>>> echo "delta1 - access time after sleep in-core: $delta1"
>>>> echo "delta2 - access time after sleep on-disk: $delta2"
>>> Why bother with deltas? if the numbers are the same, just output
>>> "same", if they are different, output "different"....
>>>
>> Fine, will do.
>>
> The only other thing is that I am not just testing the bug
> as it stands - i.e. if the atime is being lost on-disk.
> I want to test that the atime is updated appropriately.
>
> --Tim
>
Ping?
Not fussed?
Thanks,
--Tim
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2008-12-08 4:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 6:11 review: xfstests/192 atime test Timothy Shimmin
2008-11-11 22:38 ` Dave Chinner
2008-11-11 23:22 ` Timothy Shimmin
2008-11-11 23:36 ` Timothy Shimmin
2008-12-08 4:52 ` Timothy Shimmin [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=493CA7F8.9070305@sgi.com \
--to=tes@sgi.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.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