You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:02 UTC
[jira] [Updated] (BEAM-12775) Remove GCS dataflow badinput runner test
[ https://issues.apache.org/jira/browse/BEAM-12775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-12775:
-----------------------------------
This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.
> Remove GCS dataflow badinput runner test
> -----------------------------------------
>
> Key: BEAM-12775
> URL: https://issues.apache.org/jira/browse/BEAM-12775
> Project: Beam
> Issue Type: Test
> Components: runner-dataflow
> Reporter: Ryan Thompson
> Priority: P2
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Recently dataflow runner was changed to retry gcs when there was a 5XX error (like a 503 for bad input).
>
> This means that the E2E tests sdks/pthon/apache_beam/runners/dataflow/template_runner_test.py:test_bad_path
> will now retry instead of failing immediately.
>
> If retries are configurable it maybe be worthwhile to keep the test, otherwise it should be removed.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)