mirror of
https://github.com/valitydev/thrift.git
synced 2024-11-08 03:08:53 +00:00
4199377a7c
Several of the TFileTransportTest tests check wall clock time to make sure the writer thread processes operations quickly enough, and isn't hanging. However, this can easily result in false failures if we don't get enough processor time. This commit makes a few changes to reduce the number of these failures. - No longer fail if a single destructor call takes more than 500us. We only require 90% of the calls to complete in 500us. No call may take more than 100ms, though. With this change, the test passes most of the time now, even while an "fbmake opt" task is running in parallel. - In the flush_max_us tests, make sure the writer thread is started before we start recording timing. Otherwise, creating the thread could take long enough to throw off the numbers for the first fsync() call. Also tested with the pthread_cond_signal() in the TFileTransport destructor commented out, to make sure the test still fails properly when the destructor takes too long. git-svn-id: https://svn.apache.org/repos/asf/incubator/thrift/trunk@1005155 13f79535-47bb-0310-9956-ffa450edef68 |
||
|---|---|---|
| .. | ||
| AllProtocolTests.cpp | ||
| AllProtocolTests.tcc | ||
| Benchmark.cpp | ||
| DebugProtoTest_extras.cpp | ||
| DebugProtoTest.cpp | ||
| DenseProtoTest.cpp | ||
| GenericHelpers.h | ||
| JSONProtoTest.cpp | ||
| Makefile.am | ||
| OptionalRequiredTest.cpp | ||
| SpecializationTest.cpp | ||
| TBufferBaseTest.cpp | ||
| TFDTransportTest.cpp | ||
| TFileTransportTest.cpp | ||
| ThriftTest_extras.cpp | ||
| TMemoryBufferTest.cpp | ||
| TPipedTransportTest.cpp | ||
| TransportTest.cpp | ||
| UnitTestMain.cpp | ||
| ZlibTest.cpp | ||