[#84280] [Ruby trunk Bug#14181] hangs or deadlocks from waitpid, threads, and trapping SIGCHLD — nobu@...
Issue #14181 has been updated by nobu (Nobuyoshi Nakada).
3 messages
2017/12/15
[#84398] [Ruby trunk Bug#14220] WEBrick changes - failures on MSWIN, MinGW — Greg.mpls@...
Issue #14220 has been reported by MSP-Greg (Greg L).
3 messages
2017/12/22
[#84472] Re: [ruby-dev:50394] [Ruby trunk Bug#14240] warn four special variables: $; $, $/ $\ — Eric Wong <normalperson@...>
Shouldn't English posts be on ruby-core instead of ruby-dev?
3 messages
2017/12/26
[ruby-core:84108] [Ruby trunk Feature#13726] PATCH: Windows builds - fractional second file times
From:
lars@...
Date:
2017-12-06 11:09:42 UTC
List:
ruby-core #84108
Issue #13726 has been updated by larskanis (Lars Kanis).
@kubo I had the same concern, but tried the latest [RubyInstaller snapshot](https://ci.appveyor.com/project/larskanis/rubyinstaller2-hbuor/branch/master/job/4gi3xnklucahhep6/artifacts). It proves that get_systemtime() is called somewhere as part of the initialization.
```cmd
$ ruby --disable-gems -e "p File.mtime('README').usec"
657156
$ ruby -v
ruby 2.5.0dev (2017-12-05 trunk 61034) [x64-mingw32]
```
----------------------------------------
Feature #13726: PATCH: Windows builds - fractional second file times
https://bugs.ruby-lang.org/issues/13726#change-68206
* Author: MSP-Greg (Greg L)
* Status: Closed
* Priority: Normal
* Assignee: usa (Usaku NAKAMURA)
* Target version:
----------------------------------------
At present, I believe Windows builds have integer seconds resolution on File times.
Attached are three patches that seem to correct the issue. The numbered patches are best applied in order.
The c source patches were created by kubo (Kubo Takehiro); I created the spec patch, along with some testing.
All related tests (run parallel) pass on my system for MinGW builds and x64-mswin64_140 builds. I did some checks with Appveyor, and there may be issues with the logger tests, due to the fact that the tests are very time sensitive (I ran -j3 on a quad system, Appveyor runs -j2 on a dual core).
I believe file time values are stored with 100 ns resolution, but times have 100 袖s resolution. This was the reason for some of the changes to the tests, as time appears to be truncated (floor), as opposed to round.
I would appreciate if consideration could be given to adding this (or similar) code. Thank you.
---Files--------------------------------
02-file-utime.patch (5.53 KB)
spec-rubyspec-core-file-time.patch (2.99 KB)
01-time-subsec.patch (15.2 KB)
spec-rubyspec-core-file-time.patch (3.28 KB)
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>