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>
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}' ''
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}' ''