On 4/17/2017 1:55 PM, Ihar Hrachyshka wrote:
But since it's not executed anywhere in tempest gate, even as
non-voting (?), it's effectively dead code that may be long broken
without anyone knowing. Of course there are consumers of the tests
downstream, but for those consumers it's a tough call to
On Mon, Apr 17, 2017 at 7:58 PM Ihar Hrachyshka wrote:
> On Mon, Apr 17, 2017 at 9:35 AM, Jordan Pittier
> wrote:
> > 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 t
On Mon, Apr 17, 2017 at 11:55:28AM -0700, Ihar Hrachyshka wrote:
> On Mon, Apr 17, 2017 at 9:35 AM, Jordan Pittier
> wrote:
> > 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
On Mon, Apr 17, 2017 at 9:35 AM, Jordan Pittier
wrote:
> 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, thos
On Mon, Apr 17, 2017 at 6:50 AM, Ihar Hrachyshka
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
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/ch
