One of the recent Signal changes made these two tests fail. It looks like something simple in the string representation changed that caused these errors. But it would be good if someone more familiar with the Signal changes could take a look. There were 2 failures: 1) testSingleToString(frysk.sys.TestSignalSet)junit.framework.ComparisonFailure: SIGHUP set expected:<......> but was:<...(1)...> at frysk.sys.TestSignalSet.testSingleToString(TestRunner) at frysk.junit.Runner.runCases(TestRunner) at frysk.junit.Runner.runTestCases(TestRunner) at TestRunner.main(TestRunner) 2) testMultiToString(frysk.sys.TestSignalSet)junit.framework.ComparisonFailure: SIGHUP+SIGUSR1 set expected:<...,SIGUSR1...> but was:<...(1),SIGUSR1(10)...> at frysk.sys.TestSignalSet.testMultiToString(TestRunner) at frysk.junit.Runner.runCases(TestRunner) at frysk.junit.Runner.runTestCases(TestRunner) at TestRunner.main(TestRunner)
oops
Fix signal ordering; remove hard-wired name tests in TestSignalSet. frysk-sys/frysk/sys/ChangeLog 2008-01-25 Andrew Cagney <cagney@redhat.com> * Signal.java-sh (compareTo(Object)): Fix ordering. * TestSignal.java (testCompareTo()): New. * TestSignalSet.java (testSingleToString()) (testMultiToString()): Do not hard-wire signal names and numbers.