On Mon, Apr 17, 2017 at 6:50 AM, Ihar Hrachyshka <[email protected]> wrote:
> Hi all, > > so I tried to inject a failure in a tempest test and was surprised > that no gate job failed because of that: > https://review.openstack.org/#/c/457102/1 > > It turned out that the test is not executed because we always ignore > all 'slow' tagged test cases: > http://logs.openstack.org/02/457102/1/check/gate-tempest- > dsvm-neutron-full-ubuntu-xenial/89a08cc/console.html#_ > 2017-04-17_01_43_39_115768 Indeed, we don't run slow tests. Many network scenarios are not run since https://review.openstack.org/#/c/439698/ > > > Question: do we execute those tests anywhere in gate, and if so, > where? (And if not, why, and how do we guarantee that they are not > broken by new changes?) > We don"t run slow tests because the QA team think that they don't bring enough value to be executed, every time and everywhere. The idea is that if some specific slow tests are of some interest to some specific openstack projects, those projects can change the config of their jobs to enable these tests. > > Ihar > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
