From: Yu Watanabe Date: Tue, 9 Jun 2020 09:27:57 +0000 (+0900) Subject: test-network: wait 2min for the bridge being in configured state X-Git-Tag: v246-rc1~184 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=60b316b1e969d3e1e54970184102bf30dda53b25;p=thirdparty%2Fsystemd.git test-network: wait 2min for the bridge being in configured state On some CIs, it may takes more than 40 seconds. Hopefully fixes #16105. --- diff --git a/test/test-network/systemd-networkd-tests.py b/test/test-network/systemd-networkd-tests.py index 5d08a7584ca..66dc46a6b4c 100755 --- a/test/test-network/systemd-networkd-tests.py +++ b/test/test-network/systemd-networkd-tests.py @@ -2797,7 +2797,8 @@ class NetworkdBridgeTests(unittest.TestCase, Utilities): with self.subTest(test=test): if test == 'no-slave': # bridge has no slaves; it's up but *might* not have carrier - self.wait_online(['bridge99:no-carrier']) + # It may take very long time that the interface become configured state. + self.wait_online(['bridge99:no-carrier'], timeout='2m') # due to a bug in the kernel, newly-created bridges are brought up # *with* carrier, unless they have had any setting changed; e.g. # their mac set, priority set, etc. Then, they will lose carrier