I doubt it was intentional...I'm sure we're just getting the full raw ms time and using that. It may represent a valid behavioral difference (i.e. maybe the specified behavior should be only checking seconds) but that seems unlikely...
Anyway, I'll leave it in your hands if you guys want to file a bug or not. On Wed, May 26, 2010 at 5:18 PM, Antoine Toulme <[email protected]> wrote: > Alex pointed me to the fact that a.mtime == b.mtime compares values to a > unit smaller than a second, while it apparently stops at the second so far > with MRI. > So we stopped doing mtime equality because it was a bad idea, but you might > want to look into this, if that change was not intended. > > > On Wed, May 26, 2010 at 15:14, Charles Oliver Nutter <[email protected]> > wrote: >> >> On Wed, May 26, 2010 at 5:06 PM, Antoine Toulme <[email protected]> >> wrote: >> > >> > >> > On Wed, May 26, 2010 at 15:02, Charles Oliver Nutter >> > <[email protected]> >> > wrote: >> >> >> >> I have not looked at the issues...they don't happen with RJB? >> > >> > No idea, because win7 and RJB kinda suck. >> >> >> >> It could >> >> be a problem with the way we implement mtime on Windows. Any update on >> >> this in the past few days? (I was out of town). >> > >> > We changed the way we test mtime. Instead of doing ==, we now use < and >> > > to >> > avoid races. >> > We still have a few failing specs re permissions. No headway on those. >> > >> >> >> >> We're looking to push JRuby 1.5.1 very soon, so if there's something >> >> to fix we need to get it in. >> > >> > So far nothing to report. >> >> If you can narrow it down to something specific broken in JRuby, we'll >> gladly fix it. >> >> - Charlie > >
