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

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

This issue was marked "stale-P2" and has not received a public comment in 14 
days. It is now automatically moved to P3. If you are still affected by it, you 
can comment and move it back to P2.

> Increase test coverage of Perfkit benchmark for Python case
> -----------------------------------------------------------
>
>                 Key: BEAM-5329
>                 URL: https://issues.apache.org/jira/browse/BEAM-5329
>             Project: Beam
>          Issue Type: Test
>          Components: testing
>            Reporter: Mark Liu
>            Priority: P3
>              Labels: beam-fixit
>
> Perfkit benchmark is defined in PerfKitBenchmarker repo (mostly 
> [here|https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/blob/master/perfkitbenchmarker/beam_benchmark_helper.py]
>  and 
> [here|https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/blob/master/perfkitbenchmarker/linux_benchmarks/beam_integration_benchmark.py])
>  but not enough test coverage to verify changes to the benchmark or it's 
> utils. Breakage can be surfaced only when scheduled Beam Postcommit job runs 
> which will directly affect performance measurement.
> We want to add more tests starting from unit tests to cover missing branches 
> and utils like Python benchmark.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to