Timers sometimes fire early on Windows

[orangemocha]

Test simple/test-timers-first-fire.js occasionally fails on Windows, because timers fire early. I have seen the timer in the test fire up to 15ms early.

This was supposed to be fixed for the most part by joyent/libuv@6ced8c2 and for small rounding errors by #7211.

When I opened the original PR against libuv (joyent/libuv#1165) it did fix the issue, but I guess that by the time it was accepted and finally merged into node (c5f5d4c) something else must have changed that still causes timers to fire early.

[orangemocha]

cc @misterdjules

[Fishrock123]

Just got a timer to fire -1.25ms early on the io.js CI...:

nodejs/node#1272 (comment)

[misterdjules]

@orangemocha Do you have an idea of how often this problem can be reproduced on Windows? Basically, is there anything we need to know to be able to reproduce it (Windows version, etc.)?

[Fishrock123]

@trevnorris mentioned that he thought the time was in us not ms.

[Fishrock123]

Also, we had an interesting post that i'm going to attempt to look into (with my limited C knowledge) about QPC floating-point rounding issues: nodejs/node#1272 (comment)

[orangemocha]

The test output is actually in ms, not us.
When I opened this issue I could repro just by running the test in a loop on a Win 8.1 machine. I just tried the same on a Windows Server 2012 R2 machine and couldn't reproduce it.
I will look into this further...

[orangemocha]

This is also flaky in v0.10 (and a2f879f marked it so).