I disabled the tests for now until Dataflow is ready to resume testing this again. The prior implementation didn't work as intended when using the portability APIs.
On Tue, Apr 9, 2019 at 9:54 AM Andrew Pilloud <[email protected]> wrote: > The nexmark issues are https://issues.apache.org/jira/browse/BEAM-7002 > > On Tue, Apr 9, 2019 at 9:50 AM Lukasz Cwik <[email protected]> wrote: > >> The SplittableDoFn failures are because of the changes associated with >> BEAM-6978. >> >> On Tue, Apr 9, 2019 at 5:05 AM Michael Luckey <[email protected]> >> wrote: >> >>> Hi, >>> >>> looks as if >>> - beam_PostCommit_Java11_ValidatesRunner_PortabilityApi_Dataflow >>> - beam_PostCommit_Java_Nexmark_Dataflow >>> - beam_PostCommit_Java_ValidatesRunner_PortabilityApi_Dataflow >>> >>> are consistently failing since a few days [1]. Those validate runner >>> tests seem to fail on SplittableDoFnTests [2]. Error might be introduced by >>> https://issues.apache.org/jira/browse/BEAM-6978 and/or >>> https://issues.apache.org/jira/browse/BEAM-7001 [3] >>> >>> Nexmark tests seems to throw NullPointerException [4] >>> >>> Someone able to have a look? >>> >>> >>> >>> [1] >>> http://104.154.241.245/d/8N6LVeCmk/post-commits-status-dashboard?refresh=30s&orgId=1 >>> [2] >>> https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_PortabilityApi_Dataflow/1078/#showFailuresLink >>> [3] >>> https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_PortabilityApi_Dataflow/1077/#showFailuresLink >>> [4] >>> https://builds.apache.org/job/beam_PostCommit_Java_Nexmark_Dataflow/2343/console >>> >>
