[
https://issues.apache.org/jira/browse/BEAM-7074?focusedWorklogId=440514&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-440514
]
ASF GitHub Bot logged work on BEAM-7074:
----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Jun/20 23:30
Start Date: 02/Jun/20 23:30
Worklog Time Spent: 10m
Work Description: boyuanzz commented on pull request #11894:
URL: https://github.com/apache/beam/pull/11894#issuecomment-637860496
> Maybe better to list the runners that should skip instead so that we don't
limit coverage for new/unknown runners?
Re: @tweise It's kind of hard to do that since we have different
configuration for the same runner. For example, `FnApiRunner` can run with
multi-worker, or cached workers. Although it's not ideal to limit a test case
to specific test suite.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 440514)
Time Spent: 1.5h (was: 1h 20m)
> FnApiRunner fails to wire multiple timer specs in single pardo
> --------------------------------------------------------------
>
> Key: BEAM-7074
> URL: https://issues.apache.org/jira/browse/BEAM-7074
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-harness
> Affects Versions: 2.11.0
> Reporter: Thomas Weise
> Priority: P2
> Labels: stale-P2
> Fix For: 2.21.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Multiple timer specs in a ParDo yield "NotImplementedError: Timers and side
> inputs."
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
