OpenStack Compute (nova)

  1. Bug #1813147
  2. Comment #50

Comment 50 for bug 1813147

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (master)

Reviewed: https://review.opendev.org/682140
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bb2b7cad294bebd6b3bdd6d10043c3c2fb038140
Submitter: Zuul
Branch: master

commit bb2b7cad294bebd6b3bdd6d10043c3c2fb038140
Author: Matt Riedemann <email address hidden>
Date: Fri Sep 13 14:58:49 2019 -0400

    Use SpawnIsSynchronousFixture in reschedule functional tests

    We see that in successful tests that are usually running some
    kind of negative or reschedule scenario that they will dump
    a stacktrace to the subunit output buffer because
    _allocate_network_async will raise an error. Too many of these
    can eventually blow up the subunit output buffer and cause
    tests to fail.

    To guard against this, we use the SpawnIsSynchronousFixture in
    the base class of two known test classes [1][2] that show a
    stacktace with _allocate_network_async in successful runs. As a
    result, one of the tests has to be fixed due to improper stubbing.

    [1] UnsupportedPortResourceRequestBasedSchedulingTest
    [2] PortResourceRequestReSchedulingTest

    Change-Id: Ib18ecaebbeccc9c9cea32ca8949175fcea0414ac
    Related-Bug: #1813147