From: "bkabrda (Bohuslav Kabrda)" <bkabrda@...>
Date: 2012-10-05T15:47:02+09:00
Subject: [ruby-core:47841] [ruby-trunk - Bug #7109][Open] File.utime doesn't set nanoseconds


Issue #7109 has been reported by bkabrda (Bohuslav Kabrda).

----------------------------------------
Bug #7109: File.utime doesn't set nanoseconds
https://bugs.ruby-lang.org/issues/7109

Author: bkabrda (Bohuslav Kabrda)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]


Hi,
I'm having a problem with File.utime on RHEL 5/CentOS 5. The File.utime method seems not to set nanoseconds properly, see the attached test case, that fails (the nanoseconds get rounded to thousand, so in fact I get microseconds). The test doesn't seem to fail on newer platforms with the same Ruby version, though (RHEL 6/CentOS 6, Fedora 17). Note, that when creating/modifying files, the nanoseconds get set and are returned properly, so it seems that they are supported by filesystem.

Sample failure:
  1) Failure:
test_utime(TestUtime) [/builddir/build/BUILD/rubygem-sprockets-2.4.5/opt/rh/ruby193/root/usr/share/gems/gems/sprockets-2.4.5/file_utime_fail.rb:10]:
Expected: 391199303
  Actual: 391199000

Any idea what might be wrong?
Thanks!


-- 
http://bugs.ruby-lang.org/