Re: Test result of frysk on EM64T FC5 [frysk-core]

[Rick Moseley <rmoseley at redhat dot com>]

Yao Qi wrote:
> It seems that the test result varies from CPU(em64t or amd64) and
> distro(FC5 or FC6T2) on X86_64.  Here is the information about the
> machine that tests running on, and test result in frysk-core.
>
> [qiyao@YZ_X86_64 ~/build-frysk/frysk-core]$ uname -a
> Linux YZ_X86_64 2.6.15-1.2054_FC5 #1 SMP Tue Mar 14 15:48:20 EST 2006
> x86_64 x86_64 x86_64 GNU/Linux
>   
Hmmmm, that is a pretty old kernel you have there.  The latest FC5 
kernel is 2.6.17-1.2174_FC5.
> [qiyao@YZ_X86_64 ~/build-frysk/frysk-core]$ cat /proc/cpuinfo
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 15
> model           : 4
> model name      :               Intel(R) Pentium(R) 4 CPU 3.20GHz
> stepping        : 1
> cpu MHz         : 3192.283
> cache size      : 1024 KB
> physical id     : 0
> siblings        : 2
> core id         : 0
> cpu cores       : 1
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 5
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall
> nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr
> bogomips        : 6394.91
> clflush size    : 64
> cache_alignment : 128
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
>
> processor       : 1
> vendor_id       : GenuineIntel
> cpu family      : 15
> model           : 4
> model name      :               Intel(R) Pentium(R) 4 CPU 3.20GHz
> stepping        : 1
> cpu MHz         : 3192.283
> cache size      : 1024 KB
> physical id     : 0
> siblings        : 2
> core id         : 0
> cpu cores       : 1
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 5
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall
> nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr
> bogomips        : 6384.48
> clflush size    : 64
> cache_alignment : 128
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
>
> [qiyao@YZ_X86_64 ~/build-frysk/frysk-core]$ gcj -v
> Using built-in specs.
> Reading specs from /usr/lib/gcc/x86_64-redhat-linux/4.1.1/libgcj.spec
> rename spec lib to liborig
> Target: x86_64-redhat-linux
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --enable-checking=release --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-libgcj-multifile
> --enable-languages=c,c++,objc,obj-c++,java,fortran,ada
> --enable-java-awt=gtk --disable-dssi
> --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
> --with-cpu=generic --host=x86_64-redhat-linux
> Thread model: posix
> gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
>   
The compiler looks to be the current one for FC5.

Might want to try with the latest kernel and see what the results for 
you are on both FC5 and FC6t2.  There was just a new kernel released for 
FC6t2 in the last day or so, it is 2.6.17-1.2600.fc6.  The latest 
compiler for FC6t2 is gcc (GCC) 4.1.1 20060828 (Red Hat 4.1.1-20).
Rick
> Time: 29.294
> There were 5 failures:
> 1)
> testTaskBlockExec(frysk.proc.TestExec)junit.framework.AssertionFailedError:
> tmp file exists
>    at frysk.proc.TestExec.testTaskBlockExec(TestRunner)
>    at frysk.junit.Runner.<init>(TestRunner)
>    at TestRunner.main(TestRunner)
> 2)
> testAttachedMultipleChildExec(frysk.proc.TestExec)junit.framework.AssertionFailedError:
> event loop run explictly stopped (assertSendExecWaitForAcks:9010
> (Sig_USR1))
>    at frysk.proc.TestLib.assertRunUntilStop(TestRunner)
>    at frysk.proc.TestLib.assertRunUntilStop(TestRunner)
>    at frysk.proc.TestLib$AckHandler.assertAwait(TestRunner)
>    at frysk.proc.TestLib$AckHandler.await(TestRunner)
>    at
> frysk.proc.TestLib$AckProcess.assertSendExecWaitForAcks(TestRunner)
>    at frysk.proc.TestExec.testAttachedMultipleChildExec(TestRunner)
>    at frysk.junit.Runner.<init>(TestRunner)
>    at TestRunner.main(TestRunner)
> 3)
> testSyscallLoop(frysk.proc.TestTaskSyscallObserver)junit.framework.AssertionFailedError:
> inSyscall (last call doesn't exit)
>    at frysk.proc.TestTaskSyscallObserver.testSyscallLoop(TestRunner)
>    at frysk.junit.Runner.<init>(TestRunner)
>    at TestRunner.main(TestRunner)
> 4)
> testSyscalls(frysk.proc.TestTaskSyscallObserver)junit.framework.AssertionFailedError:
> syscall events
>    at frysk.proc.TestTaskSyscallObserver.testSyscalls(TestRunner)
>    at frysk.junit.Runner.<init>(TestRunner)
>    at TestRunner.main(TestRunner)
> 5)
> testSyscallOpen(frysk.proc.TestTaskSyscallObserver)junit.framework.AssertionFailedError:
> in syscall
>    at frysk.proc.TestTaskSyscallObserver.testSyscallOpen(TestRunner)
>    at frysk.junit.Runner.<init>(TestRunner)
>    at TestRunner.main(TestRunner)
>
> FAILURES!!!
> Tests run: 139,  Failures: 5,  Errors: 0
>
>