THRIFT-3256 Some D test timings are too aggressive for slow machines
Client: D language
Patch: Jens Geyer
This closes #558
diff --git a/lib/d/src/thrift/internal/test/server.d b/lib/d/src/thrift/internal/test/server.d
index b5393f0..fc5e86b 100644
--- a/lib/d/src/thrift/internal/test/server.d
+++ b/lib/d/src/thrift/internal/test/server.d
@@ -102,7 +102,7 @@
servingCondition.wait();
cancel.trigger();
- enforce(doneCondition.wait(dur!"msecs"(100)));
+ enforce(doneCondition.wait(dur!"msecs"(3*1000)));
serverThread.join();
}
}
diff --git a/lib/d/src/thrift/transport/file.d b/lib/d/src/thrift/transport/file.d
index 9aebd82..cb8bcd7 100644
--- a/lib/d/src/thrift/transport/file.d
+++ b/lib/d/src/thrift/transport/file.d
@@ -1076,7 +1076,7 @@
// If any attempt takes more than 500ms, treat that as a fatal failure to
// avoid looping over a potentially very slow operation.
- enforce(sw.peek().msecs < 500,
+ enforce(sw.peek().msecs < 1500,
text("close() took ", sw.peek().msecs, "ms."));
// Normally, it takes less than 5ms on my dev box.
@@ -1084,7 +1084,7 @@
// longer. Additionally, on a Windows Server 2008 instance running in
// a VirtualBox VM, it has been observed that about a quarter of the runs
// takes (217 ± 1) ms, for reasons not yet known.
- if (sw.peek().msecs > 5) {
+ if (sw.peek().msecs > 50) {
++numOver;
}