Bug 3835 - testStressAbandon(frysk.proc.TestAbandon)ptrace: No such process
Summary: testStressAbandon(frysk.proc.TestAbandon)ptrace: No such process
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
: 3822 3836 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-01-05 21:32 UTC by Nurdin Premji
Modified: 2007-01-11 15:59 UTC (History)
0 users

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

Attachments
compressed Log output of testStressAbandon (17.92 KB, application/x-bzip)
2007-01-05 21:48 UTC, Nurdin Premji 		Details
View All 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-05 21:32:50 UTC 
./frysk-core/TestRunner -r 100 -console frysk=FINEST
frysk.proc.TestAbandon.testStressAbandon

produces the error:

testStressAbandon(frysk.proc.TestAbandon)ptrace: No such process
   at frysk.sys.Errno.throwErrno(TestRunner)
   at frysk.sys.Ptrace$PtraceThread.notifyPtraceThread(TestRunner)
   at frysk.sys.Ptrace.detach(TestRunner)
   at frysk.proc.LinuxPtraceTask.sendDetach(TestRunner)
   at
frysk.proc.LinuxPtraceTaskState$Attached$WaitForUnblock.handleDetach(TestRunner)
   at frysk.proc.Task.performDetach(TestRunner)
   at frysk.proc.LinuxPtraceProcState$Detaching.<init>(TestRunner)
   at frysk.proc.LinuxPtraceProcState$3.handleDetach(TestRunner)
   at frysk.proc.Proc$7.execute(TestRunner)
   at frysk.event.EventLoop.runEventLoop(TestRunner)
   at frysk.event.EventLoop.runPolling(TestRunner)
   at frysk.proc.TestLib.assertRunUntilStop(TestRunner)
   at frysk.proc.TestLib.assertRunUntilStop(TestRunner)
   at frysk.proc.TestAbandon.testStressAbandon(TestRunner)
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runArchCases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner)
Comment 1 Nurdin Premji 2007-01-05 21:34:33 UTC 
*** Bug 3822 has been marked as a duplicate of this bug. ***
Comment 2 Nurdin Premji 2007-01-05 21:36:24 UTC 
*** Bug 3836 has been marked as a duplicate of this bug. ***
Comment 3 Nurdin Premji 2007-01-05 21:48:25 UTC 
Created attachment 1476 [details]
compressed Log output of testStressAbandon
Comment 4 Andrew Cagney 2007-01-10 06:46:52 UTC 
Nurdin,
How hard would it be to put the stress test in a StressAbandon file?  That way
it's only run when --stress is specified to TestRunner/junit.
Andrew
Comment 5 Nurdin Premji 2007-01-10 15:18:30 UTC 
(In reply to comment #4)
> Nurdin,
> How hard would it be to put the stress test in a StressAbandon file?  That way
> it's only run when --stress is specified to TestRunner/junit.
> Andrew

Done, new file StressTestAbandon contains stressTestAbandon.
Comment 6 Andrew Cagney 2007-01-11 11:53:25 UTC 
Did you mean "StressAbandon.java" and testAbandon()?  Otherwize the --stress
flag won't make the test run.
Comment 7 Nurdin Premji 2007-01-11 15:59:58 UTC 
Uh yeah, StressTestAbandon.java and testStressAbandon() is what I had submitted
it as, it runs with TestRunner --stress