LSB Result: Difference between revisions
From Yocto Project
Jump to navigationJump to search
Jingdong Lu (talk | contribs) No edit summary |
Jingdong Lu (talk | contribs) |
||
| Line 64: | Line 64: | ||
==Analysis of result== | ==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. | |||
* '''[[LSB_Bug_tracker | Known problem]]''': Known problem means it is a bug of LSB itself and we can find trace these bugs on http://bugs.linuxbase.org. In next page we give a summary of known problems. | |||
* '''Failures(need to fix)''' ||: Real failures we should fix them | |||
x86-32 (emenlw) | x86-32 (emenlw) | ||
{|border="1" | {|border="1" | ||
Revision as of 10:07, 25 May 2011
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. In next page we give a summary of known problems.
- Failures(need to fix) ||: Real failures we should fix them
x86-32 (emenlw)
| 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 |
