What does the second reading timing info contain? What might cause the second read to fail while the first passes?
It’s most likely that one of the WebStone clients died before it could report results to the webmaster. We’ve squashed many circumstances in which this happens, but bugs continue to appear, especially on systems we haven’t tested. We can’t do much for this kind of problem without debugging traces. Edit testbed, and set the DEBUG parameter to DEBUG=-d, so that debugging info will be written to files named /tmp/webstone-debug.