testing: Make timing for TKM rekey scenarios a bit more stable
In particular for the first one randomization could trigger an additional rekeying, which let the "Adding ESA ..." check fail. But even without randomization (could be seen in the second scenario that already uses `rand_time=0`) 4 seconds can apparently be too low some time.
This commit is contained in:
1 parent
af28aac85f
commit
7e310e3425
5 files changed
+7
-5
No files matched your search
@@ -14,7 +14,7 @@
|
||||
<ip>192.168.0.2</ip>
|
||||
</remote>
|
||||
<lifetime>
|
||||
<soft>4</soft>
|
||||
<soft>5</soft>
|
||||
<hard>60</hard>
|
||||
</lifetime>
|
||||
</policy>
|
||||
|
||||
Reference in new issue
Block a user