Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-12-06 Thread Maximilian Michels
        >          >     Will give it another look tomorrow. >          >          > >          >          >     Thanks, >          >          >     Max >          >          > >          >          >     On 22.11.18 13:07, Maximilian Michels wrote: >          &

Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-12-05 Thread Alex Amato
> in the Flink > > > > Runner but in the way the tests utilizes the > EMBEDDED > > > environment to > > > > run > > > > multiple portable jobs

Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-12-05 Thread Maximilian Michels
18 13:07, Maximilian Michels wrote: >          >      > Hi Alex, >          >      > >          >      > The test seems to have gotten flaky after we merged >         support for >          >     portable >          >      > time

Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-12-04 Thread Alex Amato
t is >> > independent of >> > > the test type (batch and streaming have different >> > implementations). >> > > >> > > Will give it another look tomorrow. >> > > >> > >

Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-12-04 Thread Alex Amato
orrow. > > > > > > Thanks, > > > Max > > > > > > On 22.11.18 13:07, Maximilian Michels wrote: > > > > Hi Alex, > > > > > > > > The test seems to have g

Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-11-30 Thread Maximilian Michels
>      > Thanks, >      > Max >      > >      > On 21.11.18 23:56, Alex Amato wrote: >      >> Hello, I have noticed >      >> that org.apache.beam.runners.flink.PortableTimersExecutionTest >     is very >      >> flakey, and repro'd this

Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-11-27 Thread Kenneth Knowles
orrow. >> > >> > Thanks, >> > Max >> > >> > On 22.11.18 13:07, Maximilian Michels wrote: >> > > Hi Alex, >> > > >> > > The test seems to have gotten flaky after we merged supp

Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-11-27 Thread Alex Amato
le > > > timers in Flink's batch mode. > > > > > > Looking into this now. > > > > > > Thanks, > > > Max > > > > > > On 21.11.18 23:56, Alex Amato wrote: > > >> Hello, I have

Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-11-26 Thread Maximilian Michels
ged support for portable > timers in Flink's batch mode. > > Looking into this now. > > Thanks, > Max > > On 21.11.18 23:56, Alex Amato wrote: >> Hello, I have noticed >> that org.apache.beam.runners.flink.Por

Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-11-26 Thread Alex Amato
ato wrote: > >> Hello, I have noticed > >> that org.apache.beam.runners.flink.PortableTimersExecutionTest is very > >> flakey, and repro'd this test timeout on the master branch in 40/50 > runs. > >> > >> I filed a JIRA issue: BEAM-6111 > >>

Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-11-22 Thread Maximilian Michels
Amato wrote: Hello, I have noticed that org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey, and repro'd this test timeout on the master branch in 40/50 runs. I filed a JIRA issue: BEAM-6111 <https://issues.apache.org/jira/browse/BEAM-6111>. I was just wondering if

Re: org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-11-22 Thread Maximilian Michels
Hi Alex, The test seems to have gotten flaky after we merged support for portable timers in Flink's batch mode. Looking into this now. Thanks, Max On 21.11.18 23:56, Alex Amato wrote: Hello, I have noticed that org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey

2018-11-21 Thread Alex Amato
Hello, I have noticed that org.apache.beam.runners.flink.PortableTimersExecutionTest is very flakey, and repro'd this test timeout on the master branch in 40/50 runs. I filed a JIRA issue: BEAM-6111 <https://issues.apache.org/jira/browse/BEAM-6111>. I was just wondering if anyone kn