Bug 1421 - TestLib.StopEventLoopOnProcDestroy relies on parentless sub-processes
Summary: TestLib.StopEventLoopOnProcDestroy relies on parentless sub-processes
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P1 normal
Target Milestone: ---
Assignee: Andrew Cagney
URL:
Keywords:
Depends on:
Blocks: 1631
  Show dependency treegraph
 
Reported: 2005-10-05 03:55 IST by Andrew Cagney
Modified: 2005-10-29 15:40 IST (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2005-10-05 03:55:16 IST
The current code, when it creates a sub process, does not set the parent field
(proc.parent == null).  The existing StopEventLoopOnProcDestroy is relying on
that behavour.

It needs to be replaced by something that instead matches a specific PID exiting.
Comment 1 Andrew Cagney 2005-10-05 18:14:40 IST
2005-10-05  Andrew Cagney  <cagney@redhat.com>

        * TestLib.java: For StopEventLoopOnProcDestroy, check that the
        proc is a child of frysk using getSelf.
        * TestExiting.java, TestTerminated.java: Ditto for
        ProcCreatedObserver.

        * TestLib.java: For ProcCounter, replace numberAdded and
        numberRemoved with getAdjustNumberAdded and
        getAdustedNumberRemoved.  Add getAdjustedHostProcPoolSize.
        * TestRun.java, TestFork.java: Update