diff options
| author | Donald Sharp <sharpd@nvidia.com> | 2021-10-13 14:12:51 -0400 |
|---|---|---|
| committer | Donald Sharp <sharpd@nvidia.com> | 2021-10-13 14:12:51 -0400 |
| commit | f786c3ee29c415fdd2ee014c1dd0c40636acbd6a (patch) | |
| tree | 773b402458a029533b456ab126af967bd28981de /lib/filter_cli.c | |
| parent | c9adeefcfa459dc84116d59bd23600851e1e6887 (diff) | |
tests: BFD timing tests under system load need more leeway
We have this pattern in this test:
# Let's kill the interface on rt2 and see what happens with the RIB and BFD on rt1
tgen.gears["rt2"].link_enable("eth-rt1", enabled=False)
# By default BFD provides a recovery time of 900ms plus jitter, so let's wait
# initial 2 seconds to let the CI not suffer.
topotest.sleep(2, 'Wait for BFD down notification')
router_compare_json_output(
"rt1", "show ip route ospf json", "step3/show_ip_route_rt2_down.ref", 1, 0
)
Under a heavy CI load, interface down events and then reacting to them may not actually
happen within 2 seconds. Allow some more grace time in the test to ensure that we
react to it in an appropriate manner.
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'lib/filter_cli.c')
0 files changed, 0 insertions, 0 deletions
