The test was couting both wake up, after 0 msec, of pinctrl thread
but also of main thread.
Note that the test might already been fixed by commit [0] or [1],
which drastically reduced number of wake up for the pinctrl thread.
[0] pinctrl: Fix garp_rarp waking up pinctrl thread too often.
[1] pinctrl: Fix ip_mcast_sync waking up pinctrl thread too often.
Fixes: aae6b83f192f ("pinctrl: Avoid waking-up pinctrl thread too often.")
Signed-off-by: Xavier Simonart <[email protected]>
---
tests/system-ovn.at | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/system-ovn.at b/tests/system-ovn.at
index e87cb8820..1b7dd6ddb 100644
--- a/tests/system-ovn.at
+++ b/tests/system-ovn.at
@@ -5030,7 +5030,7 @@ AT_CHECK([test 50 -gt $(ovn-appctl -t ovn-controller
coverage/read-counter pinct
# Check that we do not get too many immediate wake up.
# Tolerate a few for any race conditions.
-AT_CHECK([test 5 -gt `cat ovn-controller.log | \
+AT_CHECK([test 5 -gt `grep ovn_pinctrl0 ovn-controller.log | \
grep -c "wakeup due to 0-ms timeout at controller/pinctrl.c:"`])
OVN_CLEANUP_CONTROLLER([hv1])
--
2.47.1
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
