You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2023/08/10 22:36:00 UTC
[jira] [Updated] (FLINK-32239) Unify TestJvmProcess and TestProcessBuilder
[ https://issues.apache.org/jira/browse/FLINK-32239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-32239:
-----------------------------------
Labels: stale-assigned starter (was: starter)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see 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 remove the label and add a comment updating the community on your progress. If this issue is waiting on feedback, please consider this a reminder to the committer/reviewer. Flink is a very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone else may work on it.
> Unify TestJvmProcess and TestProcessBuilder
> -------------------------------------------
>
> Key: FLINK-32239
> URL: https://issues.apache.org/jira/browse/FLINK-32239
> Project: Flink
> Issue Type: Technical Debt
> Components: Test Infrastructure
> Reporter: Chesnay Schepler
> Assignee: Samrat Deb
> Priority: Minor
> Labels: stale-assigned, starter
> Fix For: 1.18.0
>
>
> Both of these utility classes are used to spawn additional JVM processes during tests, and contain a fair bit of duplicated logic. We can unify them to ease maintenance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)