3
0
mirror of https://git.kernel.org/pub/scm/network/wireless/iwd.git synced 2024-12-30 06:02:39 +01:00
iwd/autotests/testWPA2
Andrew Zaborowski c73575585b autotests: Remove del wd at the end function pattern
Don't use del wd to dereference the IWD instance at the end of the function
where it has been defined in the first place as at this point wd is about
to have its reference count decreased anyway (the variable's scope is
ending) so it's pointless (but didn't hurt).

Relying on the __del__ destructor to kill the IWD process in those tests
it has been started in the constructor is a bit of a hack in the first
place, because the destructor is called on garbage collection and even
through CPython does this on the refcount reaching 0, this is not
documented and there's no guideline on when it should happen or if it
should happen at all.  So it could be argued that we should keep the del
wd statemenets to be able to easily replace all of them with a call to a
new method.  But most of them are not placed so that they're guaranteed
to happen on test success or failure.  It would probably be easier to do
this and other housekeeping in a base class and make the tests its
subclasses.  Also some of these tests don't really need to launch iwd
themselves, since IWD now tracks changes in the known network files I
think IWD only really needs to be killed between tests when main.conf
changes.
2019-04-22 18:20:01 -05:00
..
connection_test.py auto-t: update tests to use get_ordered_network call 2018-12-14 13:47:00 -06:00
failure_test.py auto-t: update tests to use get_ordered_network call 2018-12-14 13:47:00 -06:00
hw.conf auto-t: Add WPA test 2016-10-03 14:18:01 -05:00
password_test.py autotests: Remove del wd at the end function pattern 2019-04-22 18:20:01 -05:00
ssidCCMP.conf auto-t: Add WPA test 2016-10-03 14:18:01 -05:00