Pablo, thanks for taking this up. It is indeed exciting to see things moving forward on the Python side (state and timer support as well).
Still, we depend on the green CI status. Just to illustrate how breakage can negatively affect even folks not immediately working on Python, consider the portability work: For many changes we need the runner build (such as Flink) as well as the Python SDK to be in good shape. Either of the two breaks and the big search begins :) Thanks, Thomas On Fri, Sep 21, 2018 at 9:11 AM Pablo Estrada <pabl...@google.com> wrote: > I investigated. This failure comes from the activation of > apache_beam.pipeline_test in Python 3 unit tests. > > I have https://github.com/apache/beam/pull/6464 out to fix this. > > In any case, it's very exciting that we have some unit tests running on > Py3 : ) > Best > -P. > > On Fri, Sep 21, 2018 at 6:40 AM Maximilian Michels <m...@apache.org> wrote: > >> Hi, >> >> The Python PreCommit tests are currently broken. Is anybody looking into >> this? >> >> Example: >> >> https://builds.apache.org/job/beam_PreCommit_Python_Commit/1308/#showFailuresLink >> JIRA: https://issues.apache.org/jira/browse/BEAM-5458 >> >> I'm sure this was just an accident. No big deal but let's make sure >> PreCommit passes when merging. A broken PreCommit means that we can't >> merge any other changes with confidence. >> >> Thanks, >> Max >> >
