Bug 5902 - kernel breaks frysk test suite
Summary: kernel breaks frysk test suite
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
Depends on:
Blocks: 1496
  Show dependency treegraph
Reported: 2008-03-10 10:50 UTC by Mark Wielaard
Modified: 2008-03-20 19:15 UTC (History)
0 users

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Mark Wielaard 2008-03-10 10:50:02 UTC
With on x86 a make check almost always fails (x86_64 seems fine
though). Downgrading to makes make check (at least in
frysk-core) completely clean again. The tests fail (and the TestRunner gets
killed!) somewhat randomly. It is easily reproducible through something like:
./TestRunner -r 100 frysk.proc.TestTaskTerminateObserver
Which always fails within a couple of rounds with as output:
  frysk.sys.Errno$Einval: tkill: Invalid argument (task 0)
Comment 1 Andrew Cagney 2008-03-11 15:48:57 UTC
On x86-64; look the same?

Running testGetTasks(frysk.proc.TestProcGet) ...ERROR
  frysk.sys.Errno$Einval: tkill: Invalid argument (task 0, signal SIGCONT (18))
Running testGetChildren(frysk.proc.TestProcGet) ...Killed
Comment 2 Andrew Cagney 2008-03-11 21:17:22 UTC
teardown process invalid: 0
   at frysk.testbed.TearDownProcess.add(TestRunner)
   at frysk.testbed.TearDownProcess$1.build(TestRunner)
   at frysk.sys.proc.ProcBuilder.scan(TestRunner)
   at frysk.sys.proc.ProcBuilder.construct(TestRunner)
   at frysk.sys.proc.ProcBuilder.construct(TestRunner)
   at frysk.testbed.TearDownProcess.tearDown(TestRunner)
   at frysk.testbed.TestLib.tearDown(TestRunner)
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner)
Comment 3 Andrew Cagney 2008-03-11 21:39:54 UTC
This likely means that readdir of /proc/PID/task is finding a dirent entry of "0".
Comment 4 Andrew Cagney 2008-03-20 19:01:24 UTC
s/is likely/is/

This trace is from the code scaning /proc/PID/task/TID and finding 

Running testTerminateKillINT(frysk.proc.TestTaskTerminateObserver) ...WARNING:
00:00:48.970 11317.11317 frysk.sys.proc.ProcBuilder: /proc/13589/task contains
bad pid: 0
  java.lang.RuntimeException: /proc/$$/task contains bad pid (pid 0)

pushing upstrea.
Comment 5 Andrew Cagney 2008-03-20 19:15:50 UTC
Fedora https://bugzilla.redhat.com/show_bug.cgi?id=438414