So the experimental queue feature is extremely useful and a great
addition. But, including a pending patch, the tempest experimental queue
now has nine jobs involving slow heat, grenade forward, neutron
isolated, savannah, etc. There are surely more to come. This means that
each use of check experimental for tempest will waste time running many
jobs that the invoker does not care about, perhaps running much longer
than the jobs the user actually does care about. Would it be plausible
to change the behaviour so that
check experimental [regexp]
would run only those jobs on the experimental queue whose name was
matched by [regexp]? Or something like that?
-David
_______________________________________________
OpenStack-Infra mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
