From 4b8450a72b4197bbb5759b90c952cfe351ea26e8 Mon Sep 17 00:00:00 2001
From: Qi Zhao <toqizhao@gmail.com>
Date: Thu, 14 May 2015 14:58:17 -0700
Subject: [PATCH] Add a timeout interop spec
---
doc/interop-test-descriptions.md | 30 ++++++++++++++++++++++++++++--
1 file changed, 28 insertions(+), 2 deletions(-)
diff --git a/doc/interop-test-descriptions.md b/doc/interop-test-descriptions.md
index e20f5b1b6d..9dfee66864 100644
--- a/doc/interop-test-descriptions.md
+++ b/doc/interop-test-descriptions.md
@@ -517,6 +517,34 @@ Procedure:
Asserts:
* Call completed with status CANCELLED
+### timeout_on_sleeping_server
+
+This test verifies that an RPC request whose lifetime exceeds its configured timeout value will end with the DeadlineExceeded status.
+
+Server features:
+* [FullDuplexCall][]
+* [Compressable Payload][]
+* [Observe ResponseParameters.interval_us][]
+
+Procedure:
+ 1. Client calls FullDuplexCall with the following request and sets its timeout to 1ms.
+
+ ```
+ {
+ response_type: COMPRESSABLE
+ response_parameters:{
+ interval_us: 3000
+ }
+ payload:{
+ body: 27182 bytes of zeros
+ }
+ }
+ ```
+2. Server will sleep for the configured interval_us and client waits for the status.
+
+Asserts:
+* Call completed with status DeadlineExceeded.
+
### concurrent_large_unary
Status: TODO
@@ -540,8 +568,6 @@ Cancel after sent headers (ctiller - done)
Cancel after received first message (ctiller - done)
-Timeout after expire (zhaoq)
-
Zero-message streams (ejona)
Multiple thousand simultaneous calls on same Channel (ctiller - done)
--
GitLab