[Bug general/3822] New: TestFStack(StressTestFStack) ptrace: no such process during teardown.

[Bug general/3822] New: TestFStack(StressTestFStack) ptrace: no such process during teardown.

[npremji at redhat dot com]

Occassionally when running TestFStack with FINEST output I get the error (during
teardown):
Note that testStressMultiThreaded was changed to have 20 clones instead of just 7.

There was 1 error:
1) testStressMultiThreadedDetach(frysk.util.StressTestFStack)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.util.TestFStack.multiThreaded(TestRunner)
   at frysk.util.StressTestFStack.testStressMultiThreadedDetach(TestRunner)
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runArchCases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner).

Log to follow.

-- 
           Summary: TestFStack(StressTestFStack) ptrace: no such process
                    during teardown.
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: npremji at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=3822

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug general/3822] TestFStack(StressTestFStack) ptrace: no such process during teardown.

[npremji at redhat dot com]

------- Additional Comments From npremji at redhat dot com  2007-01-02 16:45 -------
Created an attachment (id=1474)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=1474&action=view)
Tail end of a very long log file.

This is the remainder of a log after the allExistingTasksCompleted method was
called.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3822

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug general/3822] TestFStack(StressTestFStack) ptrace: no such process during teardown.

[npremji at redhat dot com]

------- Additional Comments From npremji at redhat dot com  2007-01-03 21:50 -------
Seems like the process is dieing in the middle of teardown. 

Should the process be made to live longer (100 seconds as opposed to 5,
especially for debugging)

or 

Should the teardown function be modified to allow errors from dead processes to
be dropped on the floor.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3822

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug general/3822] TestFStack(StressTestFStack) ptrace: no such process during teardown.

[cagney at redhat dot com]

------- Additional Comments From cagney at redhat dot com  2007-01-05 11:44 -------
I don't think this is during tear down.

Looking at the stack backtrace, there's no reference to tearDown, but there are
references to runUntilStop.  This indicates a failure during the testcase proper.

Could the thread be exiting during a detach, or something else be causing the error?

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3822

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug general/3822] TestFStack(StressTestFStack) ptrace: no such process during teardown.

[npremji at redhat dot com]

------- Additional Comments From npremji at redhat dot com  2007-01-05 21:34 -------
Aha, this is a problem with proc.requestAbandon, I've removed the call to
proc.requestAbandon in the TestFstack testcases and added a testStressAbandon
test case to TestAbandon.

*** This bug has been marked as a duplicate of 3835 ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE


http://sourceware.org/bugzilla/show_bug.cgi?id=3822

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.