the test didn't initialize the nanosecond part of the condition timeout and so
the absolute timeout calculated from the second and nanosecond values could
become invalid depending on the pseudo-random value of the nanosecond member.
This resulted in spurious gtest failures (first seen on Ubuntu).