Bug 3925 - Multiple runs of testSingleThreadedDetached cause too many open files.
Summary: Multiple runs of testSingleThreadedDetached cause too many open files.
Status: ASSIGNED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-25 22:08 UTC by Nurdin Premji
Modified: 2007-02-16 20:43 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nurdin Premji 2007-01-25 22:08:11 UTC 
./frysk-core/TestRunner -r 1000 'testSingleThreadedDetached(frysk.util.TestFStack)'

produces the following: 

Running testSingleThreadedDetached(frysk.util.TestFStack) ...execvp: Too many
open files
25-Jan-07 4:59:09 PM frysk.proc.LinuxPtraceHost$PollWaitOnSigChld$5 terminated
WARNING: No task for pid 15,123

FAIL
  junit.framework.AssertionFailedError: event loop run explictly stopped
(startChild (Sig_USR1))

Time: 5.008
There was 1 failure:
1)
testSingleThreadedDetached(frysk.util.TestFStack)junit.framework.AssertionFailedError:
event loop run explictly stopped (startChild (Sig_USR1))
   at frysk.proc.TestLib.assertRunUntilStop(TestRunner)
   at frysk.proc.TestLib.assertRunUntilStop(TestRunner)
   at frysk.proc.TestLib$AckHandler.assertAwait(TestRunner)
   at frysk.proc.TestLib$AckHandler.await(TestRunner)
   at frysk.proc.TestLib$Child.<init>(TestRunner)
   at frysk.proc.TestLib$AckProcess.<init>(TestRunner)
   at frysk.proc.TestLib$AckProcess.<init>(TestRunner)
   at frysk.proc.TestLib$DetachedAckProcess.<init>(TestRunner)
   at frysk.util.TestFStack.testSingleThreadedDetached(TestRunner)
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runArchCases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner)

FAILURES!!!
Tests run: 1,  Failures: 1,  Errors: 0

Failed after run #203

Note that it always fails after run #203.