<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - http/tests/local/fileapi/file-last-modified-after-delete.html is flaky on mac-wk1 after r200032"
href="https://bugs.webkit.org/show_bug.cgi?id=156994#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - http/tests/local/fileapi/file-last-modified-after-delete.html is flaky on mac-wk1 after r200032"
href="https://bugs.webkit.org/show_bug.cgi?id=156994">bug 156994</a>
from <span class="vcard"><a class="email" href="mailto:beidson@apple.com" title="Brady Eidson <beidson@apple.com>"> <span class="fn">Brady Eidson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=156994#c3">comment #3</a>)
<span class="quote">> I think I see what's going on here.
>
> The File.lastModified accessor is returning a fractional number of
> milliseconds since the epoch.
> e.g., 1461624859783.417
>
> Then the test end date is rounded to an integer number of milliseconds since
> epoch.
> e.g., 1461624859788
>
> Those could very easily conflict the wrong way.
> e.g. 1461624859783.241 and 1461624859783.0 (1461624859783.49 rounded down)
>
> Gotta do the rounding on the File's return value.
>
> What's entirely unclear to me is how my change actually affected this. This
> should've been an existing problem.</span >
Never mind - it is entirely clear!
lastModifiedDate used to be a Date object, which takes care of this.
lastModified is a double, which does not.
Fixing.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>