[
https://issues.apache.org/jira/browse/BIGTOP-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567415#comment-13567415
]
Hari Shreedharan commented on BIGTOP-835:
-----------------------------------------
[~dreambird]
Here is my use-case:
Apache Flume is a long running process, it will wait for input as long as it is
not killed. So in writing some tests for Flume, I hit a situation where exec
from iTest was pretty much useless to me. The case where I just needed to wait
for a self-running source to generate the data, I could use the execWithTimeout
and in the other case where I started the process and then write data via Avro
RPC to Flume, I used the equivalent of execInBackground. Both these cases
cannot be solved with the @Test(timeout).
[~cos] If you think the execInBackground should be called fork, I am ok with
that and can do it. I don't intend to change much of the code (except maybe
renaming the methods), as I do not have the cycles to do much follow up. I was
just contributing what I already did.
Also, I don't think Bigtop has a policy on naming of patches, does it? I was
just following the convention I use in other projects.
> The shell exec method must have variants which have timeout and can run in
> background
> -------------------------------------------------------------------------------------
>
> Key: BIGTOP-835
> URL: https://issues.apache.org/jira/browse/BIGTOP-835
> Project: Bigtop
> Issue Type: Bug
> Reporter: Hari Shreedharan
> Attachments: BIGTOP-835-1.patch, BIGTOP-835-2.patch,
> BIGTOP-835-2.patch, BIGTOP-835-3.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
