[wily-proposed] --config option not respected any more (causes test failures)

Pretty much all NM integration tests fail on the wily-proposed version (1.0.4), as NM tears down the (fake) "remote" side of the hwsim wifi and veth interfaces. Turns out this is due to not respecting the local --config option any more, which blacklists these devices to avoid NM tearing them down at startup:

$ NetworkManager --log-level=debug --debug --config=/tmp/tmpyehdrfvu/NetworkManager.conf
NetworkManager-Message: <info> No config file found or given; using /etc/NetworkManager/NetworkManager.conf
NetworkManager[5227]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
[...]

In the Ubuntu packaging bzr I reverted most of the disabling of tests, and also tuned the timeouts back down to reasonable values. On top of that, if you change

--- debian/tests/nm 2015-09-04 09:06:44 +0000
+++ debian/tests/nm 2015-09-04 09:07:05 +0000
@@ -75,7 +75,8 @@
                         blacklist += ';'
                     blacklist += 'mac:%s' % f.read().strip()

- conf = os.path.join(self.workdir, 'NetworkManager.conf')
+ #conf = os.path.join(self.workdir, 'NetworkManager.conf')
+ conf = '/etc/NetworkManager/NetworkManager.conf'
         extra_main = ''
         if not auto_connect:
             extra_main += 'no-auto-default=*\n'

to work around this bug, all the tests succeed again, at least on amd64. On i386 they still fail because NM crashes right away (bug 1492126).