GTest "clock too coarse" failure despite upgraded kernel

[clarkg]

Hey,

This is the log of the test suite from running "make check" on a fresh clone following the instructions of the README:

====================================
   folly 3.2: test/test-suite.log
====================================

# TOTAL: 36
# PASS:  35
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: foreach_test
==================

[==========] Running 7 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 7 tests from Foreach
[ RUN      ] Foreach.ForEachRvalue
[       OK ] Foreach.ForEachRvalue (0 ms)
[ RUN      ] Foreach.ForEachKV
[       OK ] Foreach.ForEachKV (0 ms)
[ RUN      ] Foreach.ForEachKVBreak
[       OK ] Foreach.ForEachKVBreak (0 ms)
[ RUN      ] Foreach.ForEachKvWithMultiMap
[       OK ] Foreach.ForEachKvWithMultiMap (0 ms)
[ RUN      ] Foreach.ForEachEnumerate
[       OK ] Foreach.ForEachEnumerate (0 ms)
[ RUN      ] Foreach.ForEachEnumerateBreak
[       OK ] Foreach.ForEachEnumerateBreak (0 ms)
[ RUN      ] Foreach.ForEachRangeR
[       OK ] Foreach.ForEachRangeR (0 ms)
[----------] 7 tests from Foreach (0 ms total)

[----------] Global test environment tear-down
[==========] 7 tests from 1 test case ran. (0 ms total)
[  PASSED  ] 7 tests.
WARNING: Logging before InitGoogleLogging() is written to STDERR
F0907 03:02:39.205322  1549 Benchmark.cpp:210] Check failed: 1 == ts.tv_nsec (1 vs. 4000000) Clock too coarse, upgrade your kernel.
*** Check failure stack trace: ***

I got this on a Microsoft Azure cloud compute server with the most up-to-date Linux kernel that is not RC:

Distributor ID: Ubuntu
Description:    Ubuntu 14.04.1 LTS
Release:        14.04
Codename:       trusty

3.16.2-031602-generic

Hope I'm not just being dumb. Looks like I was still able to run sudo make install without any problems.

[ghost]

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

[ghost]

Thank you for your patience. After 30 days with no updates from the core team, we're closing out the issue. If you're still experiencing the problem described, please reopen the issue - thanks!