LSB Result

Introduction

The Linux Standard Base(LSB) was created to lower the overall costs of supporting the Linux platform. By reducing the differences between individual Linux distributions, the LSB greatly reduces the costs involved with porting applications to different distributions, as well as lowers the cost and effort involved in after-market support of those applications. (http://www.linuxfoundation.org/collaborate/workgroups/lsb)

Test Environment

• Image: core-image-lsb-qt3
• Platform: x86-32(emenlow), x86-64(), ppc(mpc8315e-rdb)

result

Below table shows the result of LSB Test on different platforms.

Test	Version	X86-32(emenlow)	X86-64()	ppc(mpc8315e-rdb)
Command Check	v 4.1.0-1	Success		Success
Library Check	v 4.1.0-1	Warning		Warning
Alsa-T2C Tests	v 4.1.0-1	Success		Success
Core Tests	v 4.1.0-1	Failures: 12		Failures: 66
Core-T2C Tests	v 4.1.0-1	Success		Success
Cpp-T2C Tests	v 4.1.0-1	Success		Success
Desktop Tests	v 4.1.0-2	Failures: 2		Failures: 24
Desktop-T2C Tests	v 4.1.0-1	Failures: 2		Failures: 17
Libstdc++ Tests	v 4.1.0-13	Success		Failures: 2
OLVER Core Tests	v 4.1.0-1	Failures: 10		Block
Perl Tests	v 4.1.0-1	Failures: 1		Failures: 1
Printing Tests	v 4.1.0-1	Failures: 1		Failures: 3
Python Runtime Tests	v 4.1.1-2	Success		Success
Qt3-Azov Tests	v 4.1.0-1	Success		Failures: 106
Qt4-Azov Tests	v 4.1.0-1	Failures: 5		Failures: 46
Xml2-Azov Tests	v 4.1.0-1	Success		Success
Xts5 Tests	v 5.1.5-38	Failures: 1		Failures: 2
Apache Tests	v 2.2.14-3	Success
Expect Tests	v 5.43.0-11	Success		Success
Groff Tests	v 1.20.1-5	Success		Success
Raptor Tests	v 1.4.19-3	Success		Success
Rsync Tests	v 3.0.6-3	Success		Success
Samba Tests	v 3.4.3-5	Success		Success
Tcl Tests	v 8.5.7-6	Success		Success
Xpdf Tests	v 1.01-10	Success		Failures: 1

Analysis of result

Below table shows the failed test cases.

• Total failures: The number of total failures after running test. It includes known problems and real failures which should be fixed.
• Known problem: Known problem means it is a bug of LSB itself and we can find trace these bugs on http://bugs.linuxbase.org. On link page we give a summary of known problems.
• Failures(need to fix) : Real failures we should fix them

x86-32 (emenlw)

We have 4 failures to fix.

• Core tests: 2
• Xts5 Tests:1

Test	Total failures	Known problem	Failures(need to fix)	Note
Core Tests	12	10	2
Desktop Tests	2	2
Desktop-T2C Tests	2	2
OLVER Core Tests	10	10
Perl Tests	1	1
Printing Tests	1	1
Qt4-Azov Tests	5	5
Xts5 Tests	1		1

ppc(mpc8315e)

We have the following failures(including "unresolved" and "failed") to fix.

Test	Total failures	Known problem	Failures(need to fix)	Note
Core Tests	66	10	47(unresolved), 8(failed), 1(unreported)
Desktop Tests	24	20	2(unresolved), 1(failed), 1 unreported
Desktop-T2C Tests	17	2	15(unresolved)
Libstdc++ Tests	2		2
OLVER Core Tests				Blocked
Perl Tests	1	1
Printing Tests	3	1	1(unresolved), 1(failure), 1(unreported)
Qt3-Azov	106		106(unresolved)
Qt4-Azov	46	1	45(unresolved)
Xts5 Tests	2		2
Xpdf Tests	1		1

• Core Tests:
  • /tset/ANSI.os/math/... : SIGILL cause 47 unresolved failures.
• OLVER Core Tests:
  • OLVER Core Tests can't be finished on mpc8315e-rdb
  • We think the reason which make test blocked is the low memory(128M on mpc8315e). Because we re-run the test case which is blocked during OLVER core tests and it can pass successfully. That is to say, if we run the single test case, it will be passed. But we run all OLVER core tests and the whole tests will be blocked. We have ever run OLVER Core Tests for nearly 50 hours and it can't finish.
  • lsb-test-olver-core may require about 512Mb of system memory (with an X server and a contemporary desktop running), as well as 2Gb of free disk space to complete a test run. The reference linkage: http://ldn.linuxfoundation.org/lsb/preparing-lsb-distribution-testing
• Qt3-Azov Tests:
  • Out of memory error cause all of the failures
• Xpdf Tests:
  • SIGILL cause Xpdf failed.

Failures tracker

We should fix the following problems. We also filed bugs for them and try to fix them.

Tests	Sub Tests	Test Number	Arch	Bug ID of yocto	Proposal suggestion
Core Tests	/tset/LSB.fhs/var/lib/lib-tc	1	x86-32, x86-64, ppc	http://bugzilla.pokylinux.org/show_bug.cgi?id=1092	http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/sudo
Core Tests	/tset/LSB.fhs/var/lib-misc/lib-misc-tc	1	x86-32, x86-64, ppc	http://bugzilla.pokylinux.org/show_bug.cgi?id=1092	http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/sudo
Xts5 Tests	/tset/Xopen/strtkysym/Test	7	x86-32, ppc	http://bugzilla.pokylinux.org/show_bug.cgi?id=1095	http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?h=jingdonglu/distro&id=c6dde065b9fafabeda6904c23118a11e99d23e08
Perl Tests	../ext/IPC/SysV/t/ipcsysv.t	294	x86-32, ppc	http://bugzilla.pokylinux.org/show_bug.cgi?id=1078	Maybe a LSB bug(we have filed it as a bug on LSB bugzilla

Known problems tracker

See details on Known problems tracker