Re: avoid fc5 kernels > kernel-2.6.17-1.2187_FC5 and < 1.2243

[Mark Wielaard <mark at klomp dot org>]

Hi Stan,

On Tue, 2006-11-21 at 15:20 -0500, Stan Cox wrote:
> On Tue, 2006-11-21 at 18:24 +0100, Mark Wielaard wrote:
> 
> > 1) testExecSyscall(frysk.proc.TestTaskSyscallObserver)

This one seems not deterministic although it fails most of the time for
me. This is http://sourceware.org/bugzilla/show_bug.cgi?id=3244

> Running testLinuxIa32(frysk.proc.TestSyscallsWithAudit) ...FAIL
> Running testLinuxPPC(frysk.proc.TestSyscallsWithAudit) ...FAIL
> Running testLinuxPPC64(frysk.proc.TestSyscallsWithAudit) ...FAIL
> Running testLinuxX86_64(frysk.proc.TestSyscallsWithAudit) ...FAIL

These do pass for me on a similar system. What version of libaudit do
you have? $ rpm -q audit-libs
audit-libs-1.2.9-1.fc5
audit-libs-1.2.9-1.fc5
(Apparently I have both the i386 and x86_64 versions installed)

> Running testMultiThreadedDetached(frysk.util.TestFStack) ...FAIL
> Running testMultiThreadedAckDaemon(frysk.util.TestFStack) ...FAIL
> Running testStressMultiThreadedDetach(frysk.util.TestFStack) ...FAIL
> Running testClone(frysk.util.TestFStack) ...FAIL

So these are common failures for x86_64, but not on x86. FStack probably
tries to match the call stack precisely to what is generated on x86.

Cheers,

Mark