A recent core build failed on custom_cluster/test_hdfs_timeout.py with this test output:
When executing SynchronousOffer(), two different operation count towards the timeout. The first is submitting the task by calling Offer with the SynchronousWorkItem. The second is waiting for the task to complete by calling SynchronousWorkItem::Wait(). If the first part task takes any measurable time, then SynchronousOffer() modifies the timeout that it passes into SynchronousWorkItem::Wait() so that the total timeout is respected. The enforcement of the new timeout is correct, but it results in an incorrect error message (in this case, showing 4 seconds rather than 5).
This should pass in the original timeout and the current elapsed time. This would allow for correct enforcement with a correct error message.
This issue is flaky.