You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Yetus QA (JIRA)" <ji...@apache.org> on 2017/11/01 16:11:01 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16234300#comment-16234300 ]
Yetus QA commented on YETUS-570:
--------------------------------
(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://builds.apache.org/job/PreCommit-YETUS-Build/663/console in case of problems.
> 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
> Priority: Major
> Attachments: YETUS-570.03.patch, YETUS-570.wip.00.patch, YETUS-570.wip.01.patch, YETUS-570.wip.02.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)