unstable integration.py test

[Martin Pitt]

nplan's autopkgtests have become unstable: http://autopkgtest.ubuntu.com/packages/n/nplan/yakkety/amd64

Several tests fail like:

======================================================================
FAIL: test_bond (__main__.TestNetworkd)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/autopkgtest.QJRvMX/build.vzz/nplan-0.12/tests/integration.py", line 400, in test_bond
    ['inet 192.168.5.[0-9]+/24'])
  File "/tmp/autopkgtest.QJRvMX/build.vzz/nplan-0.12/tests/integration.py", line 300, in assert_iface_up
    self.assertRegex(out, r, out)
AssertionError: Regex didn't match: 'inet 192.168.5.[0-9]+/24' not found in '71: mybond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000\n link/ether e6:64:0d:40:0d:e0 brd ff:ff:ff:ff:ff:ff\n inet6 fe80::e464:dff:fe40:de0/64 scope link tentative \n valid_lft forever preferred_lft forever\n' : 71: mybond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000

[Martin Pitt (pitti)]

The tests work locally with all packages from -proposed, so it doesn't seem to be a hard regression in -proposed. OTOH I cannot break the test when running on the infra without any packages from -proposed, so something timing-related must have changed.

[Martin Pitt (pitti)]

Seems it disappeared as mysteriously as it appeared; with all packages from -proposed it also is not reproducible any more, so this might be a weird side effect of the half-finished readline transition.