summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNat Goodspeed <nat@lindenlab.com>2012-03-13 14:28:19 -0400
committerNat Goodspeed <nat@lindenlab.com>2012-03-13 14:28:19 -0400
commit1bdc876b790d054400240e4a4bda6d56d026cf59 (patch)
treec0e0549b746c478ff2d573adc26e184e2a81dc71 /doc
parent7d3cf544c7962ae6cc8e0e8b8e8db817e366a9cc (diff)
Increase timeout for very-large-message test.
Apparently, at least on Mac, there are circumstances in which the very-large- message test can take several times longer than normal, yet still complete successfully. This is always the problem with timeouts: does timeout expiration mean that the code in question is actually hung, or would it complete if given a bit longer? If very-large-message test fails, retry a few times with smaller sizes to try to find a size at which the test runs reliably. The default size, ca 1MB, is intended to be substantially larger than anything we'll encounter in the wild. Is that "unreasonably" large? Is there a "reasonable" size at which the test could consistently pass? Is that "reasonable" size still larger than what we expect to encounter in practice? Need more information, hence this code.
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions