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 2020/07/03 03:45:02 UTC
[jira] [Commented] (BEAM-8941) Create a common place for Load Tests
configuration
[ https://issues.apache.org/jira/browse/BEAM-8941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150713#comment-17150713 ]
Beam JIRA Bot commented on BEAM-8941:
-------------------------------------
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.
> Create a common place for Load Tests configuration
> --------------------------------------------------
>
> Key: BEAM-8941
> URL: https://issues.apache.org/jira/browse/BEAM-8941
> Project: Beam
> Issue Type: Sub-task
> Components: testing
> Reporter: Kamil Wasilewski
> Assignee: Pawel Pasterz
> Priority: P3
> Labels: stale-assigned
> Fix For: Not applicable
>
> Time Spent: 5h 50m
> Remaining Estimate: 0h
>
> The Apache Beam community maintains different versions of each Load Test. For example, right now, there are two versions of all Python Load Tests: the first one runs on Dataflow runner, and the second one runs on Flink. With the lack of a common place where configuration for the tests can be stored, the configuration is duplicated many times with minimal differences.
> The goal is to create a common place for the configuration, so that it could be passed to different files with tests (.test-infra/jenkins/*.groovy) and filtered according to needs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)