You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2017/10/28 16:16:02 UTC

[jira] [Updated] (YETUS-570) Report and optionally kill stale JVMs between unit test modules

     [ https://issues.apache.org/jira/browse/YETUS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer updated YETUS-570:
-----------------------------------
    Attachment: YETUS-570.wip.00.patch

wip-00:
* This is a WIP, not fully debugged, etc.
* Adds two bash coproc's:
** #1 counts the number of processes/java native threads
** #2 counts processes with given names and optionally kills them aka reaper

Both of these features only work under bash 4.x.  The counter only works in Docker mode and therefore Linux.

By default, the reaper is Docker-only.  It comes in three modes off (default), watch (a counter), or kill (kill what it counted).  It currently only works under Linux but that's easily fixed.. just need to change the ps output.

> Report and optionally kill stale JVMs between unit test modules
> ---------------------------------------------------------------
>
>                 Key: YETUS-570
>                 URL: https://issues.apache.org/jira/browse/YETUS-570
>             Project: Yetus
>          Issue Type: New Feature
>          Components: Test Patch
>    Affects Versions: 0.6.0
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: YETUS-570.wip.00.patch
>
>
> YETUS-561  does a great job of preventing fork bombs and stale processes from destroying machines.  However, Yetus should do a better job of:
> a) Reporting when that happens
> b) Preventing that from happening



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)