[BEAM-10040] TestPubsubSignal not signalling success w/ Dataflow Runner

• Type: Bug
• Status: Open
• Priority: P3
• Resolution: Unresolved
• Component/s: test-failures
• Assignee: Unassigned
• Reporter: Jacob Ferriero
• Created: 20/May/20 06:30
• Updated: 04/Jun/22 16:24

Description

The issue with FhirIOReadIT seems to be some misuse of TestPubsubSignal
Example Job 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 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."

Issue Links

• links to: GitHub Pull Request #12622