summary |
shortlog |
log |
commit | commitdiff |
review |
tree
raw |
patch |
inline | side by side (from parent 1:
21690a4)
Sodium takes longer for that initial schema compilation and
now that we are using a large juniper based schema, 2m is
not long enough. In the worst case scenario where it would
never connect, then 5m is the max as the first device would
fail and the rest of the test will bail.
Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
Change-Id: I1e57bd7301b3c5f44d267489a1f8ce1c5e64531f
Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
${BASE_PORT} 17830
${NUM_WORKERS} 10
${TIMEOUT_FACTOR} 2
${BASE_PORT} 17830
${NUM_WORKERS} 10
${TIMEOUT_FACTOR} 2
+${MIN_CONNECT_TIMEOUT} 300
${DEVICES_RESULT_FILE} devices.csv
${INSTALL_TESTTOOL} True
${TESTTOOL_EXECUTABLE} ${EMPTY}
${DEVICES_RESULT_FILE} devices.csv
${INSTALL_TESTTOOL} True
${TESTTOOL_EXECUTABLE} ${EMPTY}
Run Keyword And Ignore Error CheckJVMResource.Get JVM Memory
FOR ${devices} IN RANGE ${start} ${stop+1} ${increment}
${timeout} = BuiltIn.Evaluate ${devices}*${TIMEOUT_FACTOR}
Run Keyword And Ignore Error CheckJVMResource.Get JVM Memory
FOR ${devices} IN RANGE ${start} ${stop+1} ${increment}
${timeout} = BuiltIn.Evaluate ${devices}*${TIMEOUT_FACTOR}
+ ${timeout} = Set Variable If ${timeout} > ${MIN_CONNECT_TIMEOUT} ${timeout} ${MIN_CONNECT_TIMEOUT}
Log To Console Starting Iteration with ${devices} devices
Run Keyword If "${INSTALL_TESTTOOL}"=="True" NetconfKeywords.Install_And_Start_Testtool debug=false schemas=${schema_dir} device-count=${devices}
... ELSE NetconfKeywords.Start_Testtool ${TESTTOOL_EXECUTABLE} debug=false schemas=${schema_dir} device-count=${devices}
Log To Console Starting Iteration with ${devices} devices
Run Keyword If "${INSTALL_TESTTOOL}"=="True" NetconfKeywords.Install_And_Start_Testtool debug=false schemas=${schema_dir} device-count=${devices}
... ELSE NetconfKeywords.Start_Testtool ${TESTTOOL_EXECUTABLE} debug=false schemas=${schema_dir} device-count=${devices}
[Arguments] ${current_name} ${log_response}=True
[Documentation] Operation for waiting until the device is connected.
KarafKeywords.Log_Message_To_Controller_Karaf Waiting for device ${current_name} to connect
[Arguments] ${current_name} ${log_response}=True
[Documentation] Operation for waiting until the device is connected.
KarafKeywords.Log_Message_To_Controller_Karaf Waiting for device ${current_name} to connect
- NetconfKeywords.Wait_Device_Connected ${current_name} period=0.5s timeout=120s log_response=${log_response}
+ NetconfKeywords.Wait_Device_Connected ${current_name} period=0.5s timeout=300s log_response=${log_response}
KarafKeywords.Log_Message_To_Controller_Karaf Device ${current_name} connected
Read_Python_Tool_Operation_Result
KarafKeywords.Log_Message_To_Controller_Karaf Device ${current_name} connected
Read_Python_Tool_Operation_Result