From: "jonforums (Jon Forums)" Date: 2013-01-29T13:21:08+09:00 Subject: [ruby-core:51729] [ruby-trunk - Bug #7276] TestFile#test_utime failure Issue #7276 has been updated by jonforums (Jon Forums). Nobu-san: why was r37337 required and `rb_w32_fstati64` no longer correct? Heesob: good read. After reverting r37337 as per Hiroshi's comment, I get 0 fails on trunk@38966 (Win7 32bit + mingw-w64 4.7.2) because `fstat` -> `rb_w32_fstati64` (win32/win32.c:4474) rather than `fstat` -> `_fstati64` which causes mingw-w64 to use msvcrt's `_fstat64` (i686-w64-mingw32/include/_mingw_stat64.h:12) http://msdn.microsoft.com/en-us/library/221w8e43%28v=vs.90%29.aspx Given the info you linked, do you think the current `rb_w32_fstati64` is a valid workaround? Does reverting r37337 also work for you on Win8? ---------------------------------------- Bug #7276: TestFile#test_utime failure https://bugs.ruby-lang.org/issues/7276#change-35695 Author: jonforums (Jon Forums) Status: Assigned Priority: Normal Assignee: nobu (Nobuyoshi Nakada) Category: core Target version: 2.0.0 ruby -v: ruby 2.0.0dev (2012-11-04 trunk 37467) [i386-mingw32] I'm currently travelling and am in UTC-5. I get the following `make test-all` failure on Win7 32bit with mingw-w64 gcc 4.7.2. It appears that trunk@37467 is not handling daylight savings time correctly. I'm not going to have time to try to repro on my Arch system, but can anyone else in UTC-5 (or other DST observing region) repro on either a Win7 or Linux system? [ 3509/11467] TestFile#test_utime = 0.00 s 5) Failure: test_utime(TestFile) [c:/Jenkins/workspace/ruby-trunk-svn/test/ruby/test_file.rb:287]: [ruby-core:44776]. <2011-05-27 16:10:39 -0400> expected but was <2011-05-27 15:10:39 -0400>. ... Finished tests in 641.449135s, 17.8767 tests/s, 4150.9932 assertions/s. 11467 tests, 2662651 assertions, 1 failures, 0 errors, 83 skips ruby -v: ruby 2.0.0dev (2012-11-04 trunk 37467) [i386-mingw32] -- http://bugs.ruby-lang.org/