Magnum

Functional test created too much bays

Bug #1509538 reported by hongbin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Invalid
Undecided
hongbin
Magnum mitaka-1

Bug Description

In TestKubernetesAPIs, it has six tests. As a result, it tries to create six bays to test, which is unnecessary. We can create one bay and let all the tests run on that bay.

hongbin (hongbin034)
Changed in magnum:
assignee: nobody → hongbin (hongbin034)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/239108

Changed in magnum:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on magnum (master)

Change abandoned by Hongbin Lu (<email address hidden>) on branch: master
Review: https://review.openstack.org/239108
Reason: This is an invalid fix. I tested by running this command:

tox -efunctional

This command will parallel the tests, thus creating multiple bays. The correct command is:

tox -e functional -- --concurrency=1

Then, there is only one bay created for K8sAPI

Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
Tom Cammann (tom-cammann)
Changed in magnum:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.