This is your daily summary of Beam's current flaky tests
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20labels%20%3D%20flake)
These are P1 issues because they have a major negative impact on the community
and make it hard to
This is your daily summary of Beam's current P1 issues, not including flaky
tests
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20priority%20%3D%20P1%20AND%20(labels%20is%20EMPTY%20OR%20labels%20!%3D%20flake).
See
All of the ci-beam workers are offline, I'm not sure why. I just raised
this with infra in slack [1]. It seems likely that it is related to this
issue.
[1] https://the-asf.slack.com/archives/CBX4TSBQ8/p1624554031043200
On Thu, Jun 24, 2021 at 9:59 AM Alexey Romanenko
wrote:
> Hello,
>
> This
Hello,
This job was supposed to fail because of checkstyle issue but it’s still
running more than one day:
https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/18127/
Don’t we have any timeout for such cases?
Hi,
I went through the papers and first of all, sorry, I misinterpreted the
name, this is not specific to Cloud Dataflow. I think that the biggest
issue is how to ensure that the iterative transform can make progress
_even trough the watermark cannot make progress_ (chicken-egg problem,