Add test for RestPerfClient timeouts 43/36543/4
authorJozef Behran <jbehran@cisco.com>
Tue, 22 Mar 2016 09:39:23 +0000 (10:39 +0100)
committerJozef Behran <jbehran@cisco.com>
Tue, 22 Mar 2016 16:21:32 +0000 (17:21 +0100)
When RestPerfClient times out, it means a poor Netconf
Connector performance bug was caught. In the MDSAL Northbound
case it is reported as bug 5581, no such bugs were seen in
the other two cases so none are reported. However after the
RestPerfClient bug that causes it to hang in this situation
(see bug 5413) is fixed, the suite in itself tends to fail to
take a notice of such problems so add this specific check for
timed out threads that points the poor Netconf performance
bugs out.

Change-Id: Ib75707f517ee34f40b6c9961f90309c26870bafb
Signed-off-by: Jozef Behran <jbehran@cisco.com>
csit/suites/netconf/restperfclient/mdsal.robot

index d4c4c112ee7d67ed1f5bb9a449a1876e16e4d049..795e6e7c8e75654dbe23ec644e7863423f9b6d3f 100644 (file)
@@ -60,6 +60,8 @@ Run_RestPerfClient_Directly_On_MDSAL
     Set_Known_Bug_Id    5413
     Execute_Command_Passes    ${command} >${restperfclientlog} 2>&1
     Set_Unknown_Bug_Id
+    ${result}=    SSHLibrary.Execute_Command    grep "thread timed out" ${restperfclientlog}
+    BuiltIn.Should_Be_Equal    '${result}'    ''
     ${result}=    SSHLibrary.Execute_Command    grep "FINISHED. Execution time:" ${restperfclientlog}
     BuiltIn.Should_Not_Be_Equal    '${result}'    ''
 
@@ -101,6 +103,9 @@ Run_RestPerfClient_Through_Netconf_Connector
     BuiltIn.Log    Running restperfclient: ${command}
     Set_Known_Bug_Id    5413
     Execute_Command_Passes    ${command} >${restperfclientlog} 2>&1
+    Set_Known_Bug_Id    5581
+    ${result}=    SSHLibrary.Execute_Command    grep "thread timed out" ${restperfclientlog}
+    BuiltIn.Should_Be_Equal    '${result}'    ''
     Set_Unknown_Bug_Id
     ${result}=    SSHLibrary.Execute_Command    grep "FINISHED. Execution time:" ${restperfclientlog}
     BuiltIn.Should_Not_Be_Equal    '${result}'    ''