We don't actually are about precision, this is really a sanity
commit00c5ec101c6e9cfd32778804093e4b9017a881c5
authornoelallen@chromium.org <noelallen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 25 Jul 2013 16:48:11 +0000 (25 16:48 +0000)
committernoelallen@chromium.org <noelallen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 25 Jul 2013 16:48:11 +0000 (25 16:48 +0000)
tree2bf03a3a10399b1225ffec69b2ce15b3727ac1ad
parentb60769db8ed3169b3759f1224c1e341a88cac064
We don't actually are about precision, this is really a sanity
test that the thread was blocked and waiting for approximately
the specified amount of time.

This appears to be flaky on windows which is unsurprising due
to all the time conversions between ms, ns, us, Windows and
POSIX epoch, absolute and relative time, etc...

R=binji@chromium.org

Review URL: https://codereview.chromium.org/20166002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213647 0039d316-1c4b-4281-b951-d872f2087c98
native_client_sdk/src/libraries/nacl_io_test/event_test.cc