[
https://issues.apache.org/jira/browse/BEAM-10040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314948#comment-17314948
]
Brian Hulette commented on BEAM-10040:
--------------------------------------
I don't think we're running this test on Dataflow anymore, or at least I'm not
sure where. It's not in either PostCommit_Java_DataflowV1 or
PostCommit_Java_DataflowV2:
-
https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV1/41/testReport/org.apache.beam.sdk.io.gcp.healthcare/
-
https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV2/41/testReport/org.apache.beam.sdk.io.gcp.healthcare/
It is running on PostCommit_Java though, and quite stable there:
-
https://ci-beam.apache.org/job/beam_PostCommit_Java/lastCompletedBuild/testReport/org.apache.beam.sdk.io.gcp.healthcare/FhirIOReadIT/history/
I think that increasing the timeout was the correct course of action though.
The original timeout, 30s, would be too short for a Dataflow job. Even the new
value, 5min, is probably too short. But if this test isn't running on Dataflow,
I think this jira is obsolete.
[~data-runner0] should we be running FhirIOReadIT on Dataflow?
> TestPubsubSignal not signalling success w/ Dataflow Runner
> ----------------------------------------------------------
>
> Key: BEAM-10040
> URL: https://issues.apache.org/jira/browse/BEAM-10040
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Jacob Ferriero
> Priority: P3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The issue with FhirIOReadIT seems to be some misuse of TestPubsubSignal
> [Example
> Job|https://pantheon.corp.google.com/dataflow/jobs/us-central1/2020-05-19_19_05_19-1057064265214622054?project=apache-beam-testing]
> clearly has the expected >2000 elements added to the "waitForAnyMessage" task
> but the success signal never gets published to the results topic.
> Notably there are job level warnings about metric descriptors and [warnings
> in shuffle
> logs|https://pantheon.corp.google.com/logs/viewer?dateRangeEnd=2020-05-20T02:18:25.642Z&dateRangeStart=2020-05-20T02:05:21.347Z&expandAll=false&interval=CUSTOM&project=apache-beam-testing&resource=dataflow_step%2Fjob_id%2F2020-05-19_19_05_19-1057064265214622054×tamp=2020-05-20T02:57:46.187000000Z&logName=projects%2Fapache-beam-testing%2Flogs%2Fdataflow.googleapis.com%252Fshuffler&minLogLevel=0&customFacets=&limitCustomFacetWidth=true&scrollTimestamp=2020-05-20T02:15:27.999165390Z]
> which warns:
> "Update range task returned 'invalid argument'. Assuming lost lease for work
> with id 5061980071068333770 (expiration time: 1589940982000, now:
> 1589940923590, full status: INVALID_ARGUMENT: Http(400) Bad Request). For
> more information, see
> https://cloud.google.com/dataflow/docs/guides/common-errors.";
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
