It is one-time action. Afterwards, we treat flakes as failing tests that require investigation and fixes.
--Mikhail Have feedback <http://go/migryz-feedback>? On Wed, Jun 13, 2018 at 5:06 PM Ahmet Altay <al...@google.com> wrote: > > > On Wed, Jun 13, 2018 at 3:52 PM, Mikhail Gryzykhin <mig...@google.com> > wrote: > >> Hi Ahmet, >> >> I've checked on tests status and most of other tests are green 98% of the >> time. So I feel that we do not need any explicit actions for those tests. >> > > Is it going to be a one time action to fix existing flaky tests? Or is it > about a process to detect flaky tests in general? If it is former, Java > only makes sense to me. > > >> >> However java tests seem to have most of the problems. So I moved it to >> requirements explicitly. >> >> I do not bring in fixing failing tests as those should not require any >> specific process. >> >> --Mikhail >> >> Have feedback <http://go/migryz-feedback>? >> >> >> >
