Thank you for your response. Looking forward to the fix. On Mon, Mar 8, 2021 at 2:16 AM Reuven Lax <[email protected]> wrote:
> That test was added by mistake - it was originally added for debugging > (all it did was run forever and print its results to the log), and I didn't > mean to submit it with the PR. I'll send a PR to remove that file. > > On Sun, Mar 7, 2021 at 8:15 PM Kenneth Knowles <[email protected]> wrote: > >> It was added in https://github.com/apache/beam/pull/13802 but was not >> working: >> >> - it was not excluded from the runner v2 test suite (where it is >> detected and rejected with a good error message) so I excluded it in >> https://github.com/apache/beam/pull/14111 >> - it turns out it was also already failing on the runner v1 suite. I >> have not followed up further. >> >> Kenn >> >> On Thu, Mar 4, 2021 at 12:31 PM Boyuan Zhang <[email protected]> wrote: >> >>> +Reuven Lax <[email protected]> >>> Reuven, do you have some insights on why the test is failing? >>> >>> On Thu, Mar 4, 2021 at 12:28 PM Tomo Suzuki <[email protected]> wrote: >>> >>>> Hi Beam developers, >>>> >>>> MapClassIntegrationIT in the Java Postcommit job has been failing since >>>> Feb 27th (5 days ago). >>>> >>>> https://ci-beam.apache.org/job/beam_PostCommit_Java/7269/testReport/org.apache.beam.examples.cookbook/MapClassIntegrationIT/testDataflowMapState/history/ >>>> >>>> I checked the logs (see the ticket below) but could not identify error. >>>> The underlying Dataflow job seem to become unresponsive. >>>> >>>> Created a ticket: https://issues.apache.org/jira/browse/BEAM-11922 >>>> >>>> Does anyone know how to troubleshoot this issue? (I think we need to >>>> read the Dataflow log via Google Cloud console) >>>> >>>> -- >>>> Regards, >>>> Tomo >>>> >>> -- Regards, Tomo
