testSingleThreadedAckDaemon(frysk.util.TestFStack)junit.framework.AssertionFailedError: pending signal Sig_USR1 at frysk.proc.TestLib.tearDown(TestRunner) at frysk.junit.Runner.runCases(TestRunner) at frysk.junit.Runner.runArchCases(TestRunner) at frysk.junit.Runner.runArchCases(TestRunner) at TestRunner.main(TestRunner)
Do you run this case on FC6 or FC5? Here is what I get on FC5 x86, [qiyao@GreenOnly frysk-core]$ ./TestRunner frysk.util.TestFStack Running testSingleThreadedDetached(frysk.util.TestFStack) ...PASS Running testSingleThreadedAckDaemon(frysk.util.TestFStack) ...PASS Running testMultiThreadedDetached(frysk.util.TestFStack) ...PASS Running testMultiThreadedAckDaemon(frysk.util.TestFStack) ...PASS Running testStressMultiThreadedDetach(frysk.util.TestFStack) ...PASS Time: 3.154 OK (5 tests) [qiyao@GreenOnly frysk-core]$ uname -a Linux GreenOnly 2.6.17-1.2187_FC5 #1 Mon Sep 11 01:17:06 EDT 2006 i686 i686 i386 GNU/Linux
Yup TestRunner on the specific class seems to work for the most part, but make check and TestRunner without the class as a parameter will show failures. Means there is probably an issue with the cleanup. Also a TestRunner -r 1000 frysk.util.TestFstack should eventually show you this error.
Works on fc6 and fc5. Problem was in test that ran before it: 26-Oct-2006 frysk-core/frysk/rt/CL * tests/TestStackBacktrace.java (testThreadedBacktrace): Changed to run the eventLoop, not create a new one. Fixes bug causing tests after this to fail. (handleTask): Changed to stop eventLoop on completion.