jaketf edited a comment on pull request #11339:
URL: https://github.com/apache/beam/pull/11339#issuecomment-631203002


   The issue with FhirIOReadIT seems to be some misuse of 
[TestPubsubSignal](https://beam.apache.org/releases/javadoc/2.20.0/org/apache/beam/sdk/io/gcp/pubsub/TestPubsubSignal.html)
   [Example 
Job](https://pantheon.corp.google.com/dataflow/jobs/us-central1/2020-05-19_19_05_19-1057064265214622054?project=apache-beam-testing)
 clearly has 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&timestamp=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."; 
   ```
   the 
[docs](https://cloud.google.com/dataflow/docs/guides/common-errors#bad-request-shuffler-logs)
 say this can be ignored but smells suspicious here.
   
   
   This is orthogonal to the behavior being tested. Investigating other means 
of performing this test.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to