LSB Result
From Yocto Project
Jump to navigationJump to search
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)
result
Below table shows overall progress in LTP failures analysis for current milestone:
- total: the number of total test cases
- failures: the number of failures
- audit: the number of audited failures, which status could be:
- fixed: the number of fixed failures
- LTP: native failures
- NAB: Not-A-Bug, the number of the failures which come from miss of some packages due to the profile definition, or can't reproduce locally
- pending: the analysis is done with bug reported, but pending for final solution
- duplicated: the number of failures which are same as on other platforms which have been analyzed already
- similarity: similarity to Qemux86 which is chosen as the base. most cases are common on all targets
(click the title like "qemux86" to check detail data for that target
Status | Qemux86 | Qemux86_64 | Qemuppc | Qemuarm | Qemumips | netbook | blacksand | beagleboard | routerstation | Jasperforest (lsb-sdk) | mpc8315e-rdb | |
total | 1072 | n/a | 1071 | 1071 | 1081 | n/a | n/a | 1174 | 1182 | 1198 | ||
failures | 34 | 32 | 34 | 37 | 37 | 33 | 29 | 35 | 145 (*) | 20 | ||
audit | 100% | 100% | 100% | 100% | 100% | 100% | 100% | 100% | 0(0%) | 0(0%) | ||
fixed | 6 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | |
NAB | 26 | 1 | 1 | 4 | 1 | 2 | 1 | 0 | 0 | 0 | 0 | |
LTP | 2 | 2 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | |||
Duplicated | 0 | 29 | 33 | 29 | 29 | 31 | 28 | 35 | 0 | 13 | ||
pending | 0 | 0 | 0 | 3 | 0 | 0 | 0 | 0 | 0 | |||
similarity | 100% | 90% | 88% | 78% | 78% | 90% | 96% | 85% | 19% |
* on routerstation kernel is not configured correctly. Lots of new failures are related to IPC, which may come from lacking of some kernel options. This has been verified with newer 2.6.37 kernel recently, that only ~60 failures remaining. So the analysis is skipped for it in this cycle.