[
https://issues.apache.org/jira/browse/BEAM-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369919#comment-17369919
]
Beam JIRA Bot commented on BEAM-12230:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Re-enable FnApiDoFnRunner.testUsingMetrics
> ------------------------------------------
>
> Key: BEAM-12230
> URL: https://issues.apache.org/jira/browse/BEAM-12230
> Project: Beam
> Issue Type: Test
> Components: runner-core
> Reporter: Kenneth Knowles
> Priority: P2
> Labels: stale-P2
>
> This 150+ LOC test method has assumptions built in that are not true in the
> portable side input expansion. I was unable to determine how to adjust it. I
> am disabling it temporarily to unblock progress. The features that
> {{FnApiDoFnRunner}} implements are tested by portable ValidatesRunner suites
> and other end-to-end tests. Most likely the best way to adjust this is to
> replace it by something that does not mock out so much test setup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
