I think the previously mentioned issues are resolved now, but the python precommit still has some flakes. I filed: https://issues.apache.org/jira/browse/BEAM-9975 - PortableRunnerTest flake "ParseError: Unexpected type for Value message."
An example of this is https://builds.apache.org/job/beam_PreCommit_Python_Cron/2743/ It looks the same failure mode as https://issues.apache.org/jira/browse/BEAM-9907, but it occurs for PortableRunnerTest (and sub-classes). In BEAM-9907 it was because a PipelineOption instance was unintentionally constructed such that it read arguments from sys.argv, and in a test it parsed arguments intended for the test framework, not for Beam. I don't _think_ that's what's happening here, but I'm not sure. Could someone with more context take a look? Brian On Thu, May 7, 2020 at 11:10 AM Ahmet Altay <al...@google.com> wrote: > I am aware of the following two that contributes to precommit flakiness. > Someone is working on both. > > https://issues.apache.org/jira/browse/BEAM-9907 - ExternalTransform > https://issues.apache.org/jira/browse/BEAM-9767 - test_streaming_wordcount > flaky > > > On Thu, May 7, 2020 at 10:54 AM Brian Hulette <bhule...@google.com> wrote: > >> It looks like this is likely due to my PR for pipeline options in >> external transforms: https://github.com/apache/beam/pull/11574 >> >> I'll confirm and roll back if it is. >> >> On Thu, May 7, 2020 at 10:51 AM Pablo Estrada <pabl...@google.com> wrote: >> >>> Hi all, >>> the Precommit tests have been flaky for a couple of days due to >>> ExternalTransform tests. See >>> https://builds.apache.org/job/beam_PreCommit_Python_Cron/ - and an >>> example failure: >>> >>> https://builds.apache.org/job/beam_PreCommit_Python_Cron/2723/ >>> >>> Does somebody know about this? >>> Best >>> -P. >>> >>
