nmstate / nmstate / 3664 / 5

Ran 28 Nov 2019 07:04PM UTC

Files 34

Run time 2s

Badge

Embed ▾

Committed 28 Nov 2019 06:57PM UTC coverage: 65.395% (+0.06%) from 65.331%

Job # DOCKER_IMAGE=nmstate/fedora-nmstate-dev testflags="--test-type unit_py36"

Build Type

push

travis-ci-com

Committed by

cathay4t

Commit Message

test: Explicitly delete device even in DEACTIVATING state

The current code skips device deletion when the device is in
DEACTIVATING state. This can result in leftover software interfaces
without corresponding Network manager profile. Therefore try to remove
the device regardless of its state.

A proper fix would be to wait for Network Manager to delete it and only
do it explicitly after a timeout. However, when `NM.Device` is in
DEACTIVATING state, after registering both `NM.Device.state-change` and
`NM.Client.device-removed` signals, no callback was triggered by
NetworkManager-1.20.9-1.37c571a72a

Jira issue to  find a better solution:
https://nmstate.atlassian.net/browse/NMSTATE-280

Signed-off-by: Gris Ge <fge@redhat.com>

Run Details

2022 of 3092 relevant lines covered (65.39%)

0.65 hits per line

nmstate / nmstate / 3664 / 5

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 3664.5 (DOCKER_IMAGE=nmstate/fedora-nmstate-dev testflags="--test-type unit_py36")

nmstate / nmstate / 3664 / 5

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 3664.5 (DOCKER_IMAGE=nmstate/fedora-nmstate-dev testflags="--test-type unit_py36")

README BADGES
x