Hi list,
I understood we need to limit the number of tests and jobs that are run for
each Tempest patch because our resources are not unlimited.

In Tempest, we have 5 multinode experimental jobs:

experimental-tempest-dsvm-multinode-full-dibtest
gate-tempest-dsvm-multinode-full
gate-tempest-dsvm-multinode-live-migration
gate-tempest-dsvm-neutron-multinode-full
gate-tempest-dsvm-neutron-dvr-multinode-full

These jobs largely overlap with the non-multinode jobs. What about tagging
(with a python decorator) each test that really requires multiple nodes and
only run those tests as part of the multinode jobs ?
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to