You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/09/18 17:24:00 UTC

[jira] [Commented] (BEAM-12775) Remove GCS dataflow badinput runner test

    [ https://issues.apache.org/jira/browse/BEAM-12775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417193#comment-17417193 ] 

Beam JIRA Bot commented on BEAM-12775:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> 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
>            Assignee: Ryan Thompson
>            Priority: P2
>              Labels: stale-assigned
>          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.3.4#803005)