river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zsolt Kúti (JIRA) <j...@apache.org>
Subject [jira] Commented: (RIVER-321) Process of an interrupted test can be left over
Date Mon, 28 Sep 2009 20:00:16 GMT

    [ https://issues.apache.org/jira/browse/RIVER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760364#action_12760364

Zsolt Kúti commented on RIVER-321:

Since the problem to solve is how to kill a process on an arbritrary OS and bring this info
to the right place, it really is. As to the first part, one option is applying an OS dependant
conditional logic for the command. On unix systems this logic might be substituted with a
logic that probes possible pathes. The best would be to be able to safely rely on the kill
command being on the path. Perhaps a sanity check before starting tests is in order. The second
part could perhaps be solved by using a system property that has the command as value or an
appropriate class (QARunner?) can directly contain the logic and pass down the info.

> Process of an interrupted test can be left over
> -----------------------------------------------
>                 Key: RIVER-321
>                 URL: https://issues.apache.org/jira/browse/RIVER-321
>             Project: River
>          Issue Type: Bug
>          Components: other
>            Reporter: Zsolt Kúti
>            Priority: Minor
> In MasterHarness.runTestOtherVM() a test is launched in a separate VM. In the InterruptedException
catching a kill of the process is attempted probably with a Solaris specific path (/usr/bin).
At least on BSD systems (like mine, FreeBSD) it is under /bin.
> Perhaps improvement issue type would better fit?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message