For example, my immediate suspicion with rather little to go on would be a > versus >= issue in firing processing time triggers. Coincidentally still showing up, as in https://github.com/apache/beam/pull/8366
If we had a portable runner with TestStream support, I would suggest using it. Kenn On Fri, Apr 19, 2019 at 3:45 PM Kenneth Knowles <k...@apache.org> wrote: > What is the behavior you are seeing? > > Kenn > > On Fri, Apr 19, 2019 at 3:14 PM Ahmet Altay <al...@google.com> wrote: > >> >> >> On Fri, Apr 19, 2019 at 1:58 PM Pablo Estrada <pabl...@google.com> wrote: >> >>> Hello all, >>> I've been slowly learning a bit about life in streaming, with state, >>> timers, triggers, etc. >>> >>> The other day, I tried out a trigger pipeline that did not have the >>> behavior that I was expecting, and I am looking for feedback on whether I'm >>> missing something, or this is a bug. >>> >>> Please take a look at this unit test: >>> >>> >>> https://github.com/apache/beam/pull/8364/files#diff-38fb631ae11ed485e2b99507e96ff9ffR451 >>> >>> Is the check correct that we would expect range [1, 6) to appear twice? >>> i.e. concat([1, 6), [1, 10]) ? >>> >> >> This is what I would expect. Your test code looks good to me. Could you >> file an issue? >> >> >>> >>> I have not tested this in other runners. >>> Thanks >>> -P. >>> >>
