Bug 3187 - testProcRefresh and testExitLoosesChild fail randomly on cvs head(Sep. 8)
Summary: testProcRefresh and testExitLoosesChild fail randomly on cvs head(Sep. 8)
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: 1582
  Show dependency tree / graph
 
Reported: 2006-09-08 11:49 UTC by Yao Qi
Modified: 2007-02-02 15:43 UTC (History)
2 users (show)

See Also:
Host: x86-redhat-linux
Target: x86-redhat-linux
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 Yao Qi 2006-09-08 11:49:00 UTC 
testProcRefresh and testExitLoosesChild fail randomly on FC5,

[qiyao@GreenHouse frysk-core]$ uname -a
Linux GreenHouse 2.6.17-1.2174_FC5smp #1 SMP Tue Aug 8 16:00:39 EDT 2006 i686
i686 i386 GNU/Linux

[qiyao@GreenHouse frysk-core]$ ./TestRunner frysk.proc.TestRefresh
Running testRepeatedHostRefresh(frysk.proc.TestRefresh) ...PASS
Running testHostRefresh(frysk.proc.TestRefresh) ...PASS
Running testProcRefresh(frysk.proc.TestRefresh) ...FAIL
  junit.framework.AssertionFailedError: proc's task count after kills
expected:<2> but was:<3>
Running testRefreshAll(frysk.proc.TestRefresh) ...PASS
Running testParentChild(frysk.proc.TestRefresh) ...PASS
Running testRefreshDaemon(frysk.proc.TestRefresh) ...PASS
Running testExitLoosesChild(frysk.proc.TestRefresh) ...FAIL
  junit.framework.AssertionFailedError: daemonCheck.deleted
Running testRefreshZombie(frysk.proc.TestRefresh) ...PASS
Running testUnattachedSingleExec(frysk.proc.TestRefresh) ...PASS
Running testUnattachedMultipleExec(frysk.proc.TestRefresh) ...PASS
Time: 0.504
There were 2 failures:
1) 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.<init>(TestRunner)
   at TestRunner.main(TestRunner)
2)
testExitLoosesChild(frysk.proc.TestRefresh)junit.framework.AssertionFailedError:
daemonCheck.deleted
   at frysk.proc.TestRefresh.testExitLoosesChild(TestRunner)
   at frysk.junit.Runner.<init>(TestRunner)
   at TestRunner.main(TestRunner)
FAILURES!!!
Tests run: 10,  Failures: 2,  Errors: 0
Comment 1 Mark Wielaard 2007-02-02 15:43:06 UTC 
I am still very occasionally seeing this.