Running testIt(frysk.proc.TestSyscallSignal) ...Exception in thread "Thread-76" java.lang.NullPointerException at frysk.proc.Register.get(TestRunner) at frysk.proc.LinuxIa32$1.number(TestRunner) at frysk.proc.Task.notifySyscallEnter(TestRunner) at frysk.proc.TaskState$Running.handleSyscalledEvent(TestRunner) at frysk.proc.Task.processSyscalledEvent(TestRunner) at frysk.proc.LinuxHost$PollWaitOnSigChld$2.syscallEvent(TestRunner) at frysk.sys.Wait.waitAllNoHang(TestRunner) at frysk.proc.LinuxHost$PollWaitOnSigChld.execute(TestRunner) at frysk.event.EventLoop.runEventLoop(TestRunner) at frysk.event.EventLoop.run(TestRunner) at frysk.proc.TestSyscallSignal$EventLoopRunner.run(TestRunner) /bin/sh: line 1: 25224 Terminated ${dir}$tst FAIL: TestRunner Couldn't read runs 13
Can sometimes be replicated by running: $ ./TestRunner -r 100 frysk.proc.TestSyscallSignal
./TestRunner -r 500 frysk.proc.TestSyscallSignal always replicates it. Seems it has something to do with the number of threads or tasks forked. Do we have some leak in our test setup?
With current CVS it does happily run with ./TestRunner -r 500 frysk.proc.TestSyscallSignal but anything higher will always fails as follows: There was 1 error: 1) testIt(frysk.proc.TestSyscallSignal)pipe (24) at frysk.testbed.ForkTestLib.throwErrno(TestRunner) at frysk.testbed.ForkTestLib.fork(TestRunner) at frysk.proc.TestSyscallSignal.setUp(TestRunner) at frysk.junit.Runner.runCases(TestRunner) at frysk.junit.Runner.runArchCases(TestRunner) at frysk.junit.Runner.runTestCases(TestRunner) at TestRunner.main(TestRunner) FAILURES!!! Tests run: 1, Failures: 0, Errors: 1 Failed after run #506 Since this is always after 506 runs (on both x86 and x86_64 machines!) I suspect this is actually a dupilicate of bug #3863, just as bug #3240. *** This bug has been marked as a duplicate of 3863 ***