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.
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>? On Wed, Jun 13, 2018 at 3:49 PM Ahmet Altay <al...@google.com> wrote: > > > On Wed, Jun 13, 2018 at 3:45 PM, Mikhail Gryzykhin <mig...@google.com> > wrote: > >> Hello everybody, >> >> Thanks everyone. I didn't receive any more feedback on the design >> proposal document [1] and I believe we've reached consensus. I've added >> implementation tasks in JIRA (BEAM-4559 [2]) and will start coding soon. >> As a recap, the high-level plan is: >> >> >> - Split existing post-commit tests jobs to automatically and manually >> triggered >> - Add tracking by JIRA bugs for failing test job >> - Create document describing post-commit failures handling policies >> - Add tests status badge to PR template >> - Create dashboard for post-commit tests >> - Detect and fix flaky java tests (if any) >> >> > Why is this limited to flaky java tests? > > >> >> [1] >> https://docs.google.com/document/d/1sczGwnCvdHiboVajGVdnZL0rfnr7ViXXAebBAf_uQME >> [2] https://issues.apache.org/jira/browse/BEAM-4559 >> >> --Mikhail >> >> >> >
