[
https://issues.apache.org/jira/browse/BEAM-12775?focusedWorklogId=639844&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-639844
]
ASF GitHub Bot logged work on BEAM-12775:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Aug/21 13:26
Start Date: 19/Aug/21 13:26
Worklog Time Spent: 10m
Work Description: ryanthompson591 commented on pull request #15350:
URL: https://github.com/apache/beam/pull/15350#issuecomment-901914545
Can you merge this?
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 639844)
Time Spent: 1h 10m (was: 1h)
> 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
> Time Spent: 1h 10m
> 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)