nmstate / nmstate / 3240 / 1

Ran 28 Oct 2019 09:36AM UTC

Files 34

Run time 1s

Badge

Embed ▾

Committed 28 Oct 2019 09:13AM UTC coverage: 81.176%. First build

Job # DOCKER_IMAGE=nmstate/fedora-nmstate-dev testflags="--test-type integ --pytest-args='-x'"

Build Type

push

travis-ci

Committed by

cathay4t

Commit Message

nm ovs: Handle race problem when OVS bridge is deleting

The 'test_bridge_with_internal_interface' test case of 'nm/ovs_test.py'
might fail randomly on line:

    assert not _get_bridge_current_state()

Where _get_bridge_current_state() should return {}.

But when OVS bridge is deleted, libnm might still have the NMDevice
object for the bridge while it has empty data in it, in that case,
we got:

    {
        'bridge': {
            'port': [],
            'options': {}
        }
    }

In order to fix the above scenario, treat the data as if the interface
does not exist and return `{}`.

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

Run Details

2471 of 3044 relevant lines covered (81.18%)

0.81 hits per line

nmstate / nmstate / 3240 / 1

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 3240.1 (DOCKER_IMAGE=nmstate/fedora-nmstate-dev testflags="--test-type integ --pytest-args='-x'")

nmstate / nmstate / 3240 / 1

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 3240.1 (DOCKER_IMAGE=nmstate/fedora-nmstate-dev testflags="--test-type integ --pytest-args='-x'")

README BADGES
x