Bug 3652 - testProcRefresh(frysk.proc.TestRefresh)junit.framework.AssertionFailedError: proc's task count after kills expected:<2> but was:<3>
Summary: testProcRefresh(frysk.proc.TestRefresh)junit.framework.AssertionFailedError: ...
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks: 2654
  Show dependency tree / graph
 
Reported: 2006-12-05 03:09 UTC by Andrew Cagney
Modified: 2008-10-21 21:40 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 Andrew Cagney 2006-12-05 03:09:52 UTC 
testProcRefresh(frysk.proc.TestRefresh)junit.framework.AssertionFailedError:
proc's task count after kills expected:<2> but was:<3>
   at frysk.proc.TestRefresh.testProcRefresh(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 Andrew Cagney 2006-12-05 04:53:15 UTC 
There's a race condition with the way tasks, once joined, get removed from /proc
- at the time of the refresh only one of the tasks was removed but a probe shows
that the second later disappears.
Comment 2 Andrew Cagney 2006-12-05 05:07:32 UTC 
Downstream tracker:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218405