diff options
author | Nat Goodspeed <nat@lindenlab.com> | 2015-11-18 17:22:57 -0500 |
---|---|---|
committer | Nat Goodspeed <nat@lindenlab.com> | 2015-11-18 17:22:57 -0500 |
commit | 2ccbb77f3c3ed0965c341814daec43a666592e90 (patch) | |
tree | 69b4ff44edddadf967efa673eea5003a2e01a5e2 | |
parent | 5e111c6d00ddfa39cde84ed01afcbed2b0fed646 (diff) |
WOLF-300: Try using a smaller data volume for LLLeap tests on Windows.
-rwxr-xr-x | indra/llcommon/tests/llleap_test.cpp | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/indra/llcommon/tests/llleap_test.cpp b/indra/llcommon/tests/llleap_test.cpp index 2d88e2c676..d342dece84 100755 --- a/indra/llcommon/tests/llleap_test.cpp +++ b/indra/llcommon/tests/llleap_test.cpp @@ -36,10 +36,18 @@ StringVec sv(const StringVec& listof) { return listof; } #if defined(LL_WINDOWS) #define sleep(secs) _sleep((secs) * 1000) -#endif +// WOLF-300: It appears that driving a megabyte of data through an LLLeap pipe +// causes Windows abdominal pain such that it later fails code-signing in some +// mysterious way. Entirely suppressing these LLLeap tests pushes the failure +// rate MUCH lower. Can we re-enable them with a smaller data size on Windows? +const size_t BUFFERED_LENGTH = 100*1024; + +#else // not Windows const size_t BUFFERED_LENGTH = 1023*1024; // try wrangling just under a megabyte of data +#endif + void waitfor(const std::vector<LLLeap*>& instances, int timeout=60) { int i; |