Public bug reported: We're seeing intermittent kernel ADT test failues against network- manager due to the ColdplugWifi test timing out. This is happening across multiple releases. Here's an example from xenial:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/i386/n/network- manager/20170215_193017_bf4ec@/log.gz and another from zesty: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/i386/n/network- manager/20170307_182040_787e9@/log.gz In experimenting on zesty I've found that I can pretty easily recreate the failures by running the ColdplugWifi test in a loop, usually within 10 iterations. I've also found that if I increase the timeout in the test for reaching the activated state from 20 to 30 seconds I cannot reproduce the error. So it seems that perhaps the timeout on the test is too short and should be increased. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1671216 Title: ColdplugWifi test failures in ADT Status in network-manager package in Ubuntu: New Bug description: We're seeing intermittent kernel ADT test failues against network- manager due to the ColdplugWifi test timing out. This is happening across multiple releases. Here's an example from xenial: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/i386/n/network- manager/20170215_193017_bf4ec@/log.gz and another from zesty: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/i386/n/network- manager/20170307_182040_787e9@/log.gz In experimenting on zesty I've found that I can pretty easily recreate the failures by running the ColdplugWifi test in a loop, usually within 10 iterations. I've also found that if I increase the timeout in the test for reaching the activated state from 20 to 30 seconds I cannot reproduce the error. So it seems that perhaps the timeout on the test is too short and should be increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
