Stephan Ewen created FLINK-13033:
Summary: Unstable test ChainOrderTest
Key: FLINK-13033
URL: https://issues.apache.org/jira/browse/FLINK-13033
Project: Flink
Issue Type: Bug
Compon
So yes, the Jenkins job keeps pulling the state from Travis until it
finishes.
Note sure I'm comfortable with the idea of using Jenkins workers just to
idle for a several hours.
On 29/06/2019 14:56, Jeff Zhang wrote:
Here's what zeppelin community did, we make a python script to check the
bu
Here's what zeppelin community did, we make a python script to check the
build status of pull request.
Here's script:
https://github.com/apache/zeppelin/blob/master/travis_check.py
And this is the script we used in Jenkins build job.
if [ -f "travis_check.py" ]; then
git log -n 1
STATUS=$(cur
Hi Robert, Hi Marta,
sounds good to me, happy to review.
Cheers,
Konstantin
On Fri, Jun 28, 2019 at 3:11 PM Robert Metzger wrote:
> Great! Thanks Marta. Looking forward to review the first pull request for a
> blog post.
>
> On Fri, Jun 28, 2019 at 10:09 AM Marta Paes Moreira
> wrote:
>
> >
jasine chen created FLINK-13032:
---
Summary: Allow Access to Per-Window State in SessionWindow
ProcessWindowFunction
Key: FLINK-13032
URL: https://issues.apache.org/jira/browse/FLINK-13032
Project: Flink
jasine chen created FLINK-13031:
---
Summary: Support dynamic offset in tumbling windows
Key: FLINK-13031
URL: https://issues.apache.org/jira/browse/FLINK-13031
Project: Flink
Issue Type: Wish
Does this imply that a Jenkins job is active as long as the Travis build
runs?
On 26/06/2019 21:28, Bowen Li wrote:
Hi,
@Dawid, I think the "long test running" as I mentioned in the first email,
also as you guys said, belongs to "a big effort which is much harder to
accomplish in a short perio
