On 09/05/2012 09:03 PM, James E. Blair wrote: > Here's what I'd like to propose instead: > > 1) Make the tempest gate symmetrical -- cross-project gating works best > when all the projects gate on the same tests so that one project can't > break another.
Hmm. Well, this really is just circumventing the problems instead of fixing them IMO :) I would prefer that we run all tests for the tempest gate. > 2) Add more tests to the set of tests that get run in the > devstack/tempest gate (currently the smoke tests). It sounds like > several tests in the full suite really are breaking because of changes > in other projects -- those should probably be considered for promotion. No problems here. > 3) Modify devstack-gate to run tempest a second time (on the same host, > after completing the smoke tests), to run the rest of the suite, but > ignore the results of that for gating purposes. This way the results > will be available for every change, without affecting gating or > consuming more virtual machines. In other words, have devstack gate: > > run devstack > run smoke tests > save return code > run full suite - smoke tests > exit with saved return code > > How does that sound? Sounds like a reasonable compromise I suppose, yep. Best, -jay -- Mailing list: https://launchpad.net/~openstack-qa-team Post to : openstack-qa-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-qa-team More help : https://help.launchpad.net/ListHelp
