Ok, I see. This bug is specifically about Teardown behavior.
On Tue, Feb 27, 2018 at 1:33 PM Reuven Lax <re...@google.com> wrote: > Can you explain "unusable?" We have hundreds of direct-runner tests that > appear to still be running just fine. Is this a new regression, or old > behavior? > > > On Tue, Feb 27, 2018 at 1:30 PM Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: > >> Updated 3409 as blocker since it makes direct runner - and therefore any >> test - unusable at all (leaks+unexpected wait times + retry strategy >> required+no real alternative even for dofn now dofntester is deprecated). >> >> Le 27 févr. 2018 21:45, "Chamikara Jayalath" <chamik...@google.com> a >> écrit : >> >>> Looks like previous URL was broken. Created >>> https://s.apache.org/beam-2.4.0-burndown. >>> >>> - Cham >>> >>> On Tue, Feb 27, 2018 at 12:22 PM Robert Bradshaw <rober...@google.com> >>> wrote: >>> >>>> I'm planning on cutting the 2.4.0 release branch soon (tomorrow?). I >>>> see 13 >>>> open issues on JIRA [1], none of which are labeled as blockers. If there >>>> are any that cannot be bumped to the next release, let me know soon. >>>> >>>> - Robert >>>> >>>> >>>> [1] >>>> >>>> https://issues.apache.org/jira/browse/BEAM-3749?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%202.4.0 >>>> >>>
