Subject: Re: bug#12820: gnulib testsuite failure in latest master

From: Stefano Lattarini <[email-masked]>
Date: Wed, 07 Nov 2012 19:32:04 +0100

On 11/07/2012 07:28 PM, Paul Eggert wrote:
> On 11/07/2012 09:06 AM, Stefano Lattarini wrote:
> 
>> stat64("test-utimens.ttmp", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
>> unlink("test-utimens.ttmp")             = 0
>> nanosleep({0, 20000000}, NULL)          = 0
>> open("test-utimens.ttmp", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0600) = 3
>> close(3)                                = 0
>> stat64("test-utimens.ttmp", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
>> unlink("test-utimens.ttmp")             = 0
>> nanosleep({2, 0}, NULL)                 = 0
> 
> Well, there's something funny going on there, as this indicates that
> your files' time stamps have only 1-second or even 2-second
> resolution.  Were you running in a FAT file system or something like
> that?
>
Nope, ext3:

  $ pwd
  /devel/bleeding/src/coreutils/gnulib-tests
  $ df -T .
  Filesystem     Type 1K-blocks     Used Available Use% Mounted on
  /dev/hdb4      ext3  23293824 13885728   9408096  60% /devel

Exact kernel version:

  $ uname -r
  2.6.30-2-686

(and not custom compiled, but installed from Debian package).

> That might explain the problem.  If you were running in an
> ordinary file system like ext4, the above is a bug and should get
> tracked down and fixed.
>

HTH,
  Stefano