LTP result

Introduction

Linux Test Project (LTP) is an open source project with a goal to deliver test suites to the open source community that validate the reliability, robustness, and stability of Linux. (http://ltp.sourceforge.net)

Unlike typical desktop/server distributions, embedded linux distribution is highly customized for a specific purpose. It's not unusual to observe more failures in Yocto than in a typical desktop Linux distro like Ubuntu, etc. So the major purposes of this work are:

• to understand the reasons for existing LTP failures. If the cause is from a specific package itself, go to fix it. Or else if the error simply come from the fact that a given package doesn't exist in current profile, add the explanation here
• to track LTP test results cross Yocto releases, and ensure a declining error number for same profile
• to be the reference if Yocto users want to get a base picture

Overall trend

Overall trend tends to track the change of LTP test results along with Yocto's progress. Previous data in 0.9 is not complete and not consistent configured on all targets. So we start from 1.0-M2 as the starting point.

In below table we list total LTP failures for each architectures in each milestone: (now this wiki doesn't allow upload files. So for detail logs please refer to earlier bug link)

Milestone

sugarbay

qemux86

qemu-x86_64

qemuppc

qemuarm

qemumips

atom-pc

blacksand

beagleboard

routerstation

mpc8315e-rdb

huronriver

edgerouter

beaglebone

genericx86-64

3.1 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

20

7

3.0 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

9

n/a

19

5

2.7 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

10

n/a

16

6

2.7 M3 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

13

n/a

16

6

2.7 M2 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

10

n/a

18

8

2.7 M1 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

10

n/a

18

8

2.6 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

11

n/a

19

9

2.6 M3 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

13

n/a

21

10

2.6 M2 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

11

n/a

23

9

2.6 M1 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

11

n/a

n/a

10

2.5 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

13

n/a

25

11

2.5 M3 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

13

n/a

26

12

2.5 M2 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

13

n/a

27

12

2.5 M1 RC3 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

13

n/a

25

12

2.5 M1 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

15

n/a

26

15

2.4 RC3 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

29

n/a

18

26

2.4 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

30

n/a

17

27

2.4 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

31

n/a

34

18

27

2.4 M3 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

31

n/a

32

17

26

2.4 M2 RC3 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

27

n/a

29

15

23

2.4 M2 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

30

n/a

24

2.4 M1 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

30

n/a

22

2.3 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

18

n/a

19

17

2.3 M3 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

18

n/a

19

18

15

2.3 M2 RC3 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

38

n/a

46

31

25

2.3 M1 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

36

n/a

41

31

25

2.2 RC4 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

35

n/a

41

31

21

2.2 M3 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

33

n/a

39

26

22

2.2 M2 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

35

n/a

41

36

22

2.1 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

42

n/a

38

35

19

2.0 RC3 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

33

n/a

38

34

23

2.0 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

33

n/a

38

34

23

1.9 M3 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

33

n/a

40

33

23

1.9 M2 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

33

n/a

38

33

24

1.9 M1 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

32

n/a

36

33

24

1.8 M4 RC2 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

32

n/a

40

32

24

1.8 M3 RC3 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

32

n/a

34

32

25

1.8 M1 RC1 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

32

n/a

34

31

24

1.7 M4 RC5 20141018 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

32

n/a

33

29

22

1.7 M4 RC4 20141011 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

32

n/a

33

29

22

1.7 M2 RC1 20140730 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

35

31

25

1.7 M1 RC1 20140625 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

35

31

25

1.5.2 RC3 20140428 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

32

37

26

n/a

n/a

n/a

16

1.6 M5 RC4 20140411 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

34

n/a

35

24

1.6 M5 RC2 20140402 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

34

n/a

35

28

1.6 M5 RC1 20140326 build

28

n/a

n/a

n/a

n/a

n/a

n/a

n/a

32

40

34

n/a

1.6 M4 RC1 20140312 build

30

n/a

n/a

n/a

n/a

n/a

n/a

n/a

33

41

36

n/a

1.6 M3 RC2 20140218 build

30

n/a

n/a

n/a

n/a

n/a

n/a

n/a

34

44

36

n/a

1.6 M3 RC1 20140213 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

34

44

36

n/a

1.6 M2 RC1 20140114 build

25

n/a

n/a

n/a

n/a

n/a

n/a

n/a

29

40

30

n/a

1.5.1 RC2 20131203 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

37

29

n/a

1.6 M1 RC1 20131203 build

25

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

37

30

n/a

1.5 M5 RC6 build

21

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

40

28

n/a

1.5 M4 RC3 build

20

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

39

25

n/a

1.5 M4 RC2 build

20

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

40

25

n/a

1.4.2 RC1 build

21

n/a

n/a

n/a

n/a

n/a

n/a

n/a

25

35

19

n/a

1.5 M3 RC1 20130731 build

20

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

37

26

n/a

1.5 M2 RC1 20130703 build

20

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

25

n/a

1.4.1 RC1 20130612 build

21

n/a

n/a

n/a

n/a

n/a

n/a

n/a

23

36

19

n/a

1.5 M1 RC1 20130604 build

19

n/a

n/a

n/a

n/a

n/a

n/a

n/a

28

n/a

23

n/a

1.3.2 20130516 build

24

n/a

n/a

n/a

n/a

n/a

n/a

n/a

23

42

18

n/a

1.4 M6 RC2 20130418 build

21

n/a

n/a

n/a

n/a

n/a

n/a

n/a

23

37

19

n/a

1.4 M5 RC3 20130403 build

20

n/a

n/a

n/a

n/a

n/a

n/a

n/a

24

n/a

21

n/a

1.4 M5 RC2 20130327 build

20

n/a

n/a

n/a

n/a

n/a

n/a

n/a

24

36

19

n/a

1.4 M4 RC1 20130220 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

22

38

19

16

1.4 M3 RC2 20130131 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

24

40

23

17

1.4 M3 RC1 20130122 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

22

39

22

17

1.2.2 20130105 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

21

38

21

17

1.2.2 20121206 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

21

38

21

17

1.4 M1 RC1 20121128 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

22

39

18

17

1.2.2 20121018 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

23

40

21

17

1.3 M5 RC4 20121010 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

21

22

38

18

16

1.3 M5 RC3 20121003 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

27

22

39

18

17

1.3 M5 RC2 20120926 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

24

22

38

18

27

1.3 M4 RC3 20120916 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

13

23

40

20

15

1.3 M3 RC2 20120814 build

n/a

n/a

n/a

n/a

n/a

n/a

n/a

n/a

23

33

21

17

1.3 20120801 build

17

n/a

n/a

n/a

n/a

n/a

n/a

n/a

24

32

24

17

1.3 M2 RC1 20120712 build

18

n/a

n/a

n/a

n/a

n/a

n/a

n/a

26

32

n/a

n/a

1.1.2 20120630 build

36

n/a

n/a

n/a

n/a

n/a

n/a

n/a

41

42

29

n/a

1.2.1 20120629 build

19

n/a

n/a

n/a

n/a

n/a

n/a

n/a

23

30

22

n/a

1.3 20120613 build

27

n/a

n/a

n/a

n/a

n/a

n/a

16

33

41

30

n/a

1.3 20120606 build

n/a

n/a

n/a

n/a

n/a

n/a

15

32

39

29

n/a

Denzil (1.2 RC5)

18

n/a

n/a

n/a

n/a

n/a

n/a

21

24

30

21

n/a

Denzil (1.2 RC4)

18

n/a

n/a

n/a

n/a

n/a

n/a

21

24

30

23

n/a

1.2-M4 RC3

18

n/a

n/a

n/a

n/a

n/a

n/a

21

24

n/a

21

n/a

1.2-M4 RC2

17

n/a

n/a

n/a

n/a

n/a

n/a

21

22

28

20

n/a

1.2-M4 RC1

17

n/a

n/a

n/a

n/a

n/a

n/a

16

22

28

20

n/a

1.2-M3 RC1

17

n/a

n/a

n/a

n/a

n/a

n/a

16

22

29

20

n/a

1.1.1

36

n/a

n/a

n/a

n/a

n/a

n/a

36

41

43

41

n/a

1.2-M2 RC1

26

n/a

n/a

n/a

n/a

n/a

n/a

27

30

37

31

n/a

1.2-M1 RC2

34

n/a

n/a

34

35

33

n/a

36

39

40

38

n/a

1.0.2

n/a

n/a

35

35

35

n/a

36

137 (*)

36

n/a

1.1-M4 RC4

35

n/a

n/a

38

39

37

n/a

36

41

43

39

n/a

1.1-M4 RC3

37

n/a

n/a

37

38

37

n/a

37

41

44

39

n/a

1.1-M4 RC2

26

n/a

n/a

38

39

37

n/a

26

43

59

39

n/a

1.1-M3

27

n/a

n/a

35

37

36

n/a

28

41

57

42

n/a

1.1-M2

30

n/a

n/a

25

29

26

n/a

28

33

146 (*)

31

n/a

1.1-M1

33

n/a

n/a

26

29

26

n/a

30

34

146 (*)

32

n/a

1.0-M2

34

32

34

37

37

33

29

35

145 (*)

n/a

*: routerstation has kernel config issues. See later for detail.

general tips:

• Yocto links /tmp to /var/volatiles/tmp which is dynamically created at each boot. This causes one issue to LTP test. /var is normally not writable to non-root users, while LTP does run some test cases under non-root accounts. This causes considerable failures (~60 in qemux86) when creating temporary contents under /tmp. The workaround to this issue is to use "-d newtmpdir" when running LTP, where newtmpdir is created with full write permissions to all users.
• There's a puzzle which profile should be chosen as the test target. Now SDK is chosen because same image can work on both qemu and real hardware. LSB profile provides better result which is more desktop like but now this profile doesn't run on real hardware and lack of some development packages like gcc. For now we just keep this choice, and introduce a Not-A-Bug type to mark failures which are caused simply because related packages are missing
  • It's better to use a tmp dir from the 2nd disk which contains ltp test suite. This way it avoids some noisy disk space limitation errors
• suggest to use "-m 512" as some tests are memory stress
• suggest to disable hackbench from runtest/sched, which is not suitable to run in emulator, and simply hang
• don't use "-q" option when running ltp, which hides many useful output info

Test Configuration and Environment

LTP version: ltp-20200120

profile: core-image-sato-sdk

run command: ./runltp -p -l result.log -C result.fail -d /opt/ltp/tmp &> result.fulllog

The below table includes which LTP categories are included in the measurement:

Milestone	qemu targets	real hardware
3.1	syscalls mm ipc sched math nptl pty command	syscalls fs fsx dio io mm ipc sched math nptl pty commands

The result 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 "blacksand" to check detail data for that target

Current Milestone (3.1 RC2 build)

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1464	1460	n/a
failures		7	20	n/a

Previous Milestone

a placeholder. Once we reach a new milestone, the data under "current milestone" will be moved here.

3.0 RC2 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1429	1425	1429
failures		5	19	9

2.7 RC2 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1397	1393	1397
failures		6	16	10

2.7 M3 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1397	1393	1397
failures		6	16	13

2.7 M2 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1391	1387	1391
failures		8	18	10

2.7 M1 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1391	1387	1391
failures		8	18	10

2.6 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1373	1369	1373
failures		9	19	11

2.6 M3 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1373	1369	1373
failures		10	21	14

2.6 M2 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1373	1369	1373
failures		9	23	11

2.6 M1 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1373		1373
failures		10		11

2.5 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1374	1370	1374
failures		11	25	13

2.5 M3 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1374	1370	1374
failures		12	26	13

2.5 M2 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1374	1370	1374
failures		12	27	13

2.5 M1 RC3 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1363	1359	1363
failures		12	25	13

2.5 M1 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1365	1358	1363
failures		15	26	15

2.4 RC3 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1391	1353	1353	1353
failures	26	18		29

2.4 RC2 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1391	1353	1353	1353
failures	27	17		30

2.4 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1391	1353	1353	1353
failures	27	18	34	31

2.4 M3 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1391	1353	1353	1353
failures	26	17	32	31

2.4 M2 RC3 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1384	1346	1344	1346
failures	23	15	29	27

2.4 M2 RC2 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1384			1348
failures	24			30

2.4 M1 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1384			1348
failures	22			30

2.3 RC2 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total		1330	1330	1330
failures		17	19	18

2.3 M3 RC2 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1366	1330	1330	1330
failures	15	18	19	18

2.3 M2 RC3 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1371	1335	1335	1335
failures	25	31	46	38

2.3 M1 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1371	1335	1335	1335
failures	25	31	41	36

2.2 RC4 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1371	1335	1335	1335
failures	21	31	41	35

2.2 M3 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1371	1335	1335	1335
failures	22	26	39	33

2.2 M2 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1371	1335	1335	1335
failures	22	36	41	35

2.1 RC2 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1371	1335	1335	1335
failures	19	35	38	42

2.0 RC3 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1326	1290	1290	1290
failures	23	34	38	33

2.0 RC2 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1326	1290	1290	1290
failures	23	34	38	33

1.9 M3 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1326	1290	1290	1290
failures	23	33	40	33

1.9 M2 RC2 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1326	1290	1290	1290
failures	24	33	38	33

1.9 M1 RC2 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1326	1290	1290	1290
failures	24	33	36	32

1.8 M4 RC2 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1312	1276	1276	1276
failures	24	32	40	32

1.8 M3 RC3 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1312	1276	1276	1276
failures	25	32	34	32

1.8 M1 RC1 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1311	1311	1311	1305
failures	24	31	34	32

1.7 M4 RC5 20141018 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1291	1291	1291	1286
failures	22	29	33	32
NAB

1.7 M4 RC4 20141011 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1291	1291	1291	1286
failures	22	29	33	32
NAB

1.7 M2 RC1 20140730 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1291	1291	1291
failures	25	31	35
NAB

1.7 M1 RC1 20140625 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1291	1291	1291
failures	25	31	35
NAB

1.6 M5 RC4 20140411 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1272		1272	1272
failures	24		35	34
NAB

1.6 M5 RC2 20140402 build

Status	genericx86-64	beaglebone	edgerouter	mpc8315e-rdb
total	1272		1272	1272
failures	28		35	34
NAB

1.6 M5 RC1 20140326 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1272	1272	1272	1272	n/a
failures	n/a	32	40	34	28	n/a
fixed	n/a	n/a	n/a	n/a	n/a	n/a
NAB	n/a					n/a

1.6 M4 RC1 20140312 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1272	1272	1272	1272	n/a
failures	n/a	33	41	36	30	n/a
fixed	n/a	n/a	n/a	n/a	n/a	n/a
NAB	n/a					n/a

1.6 M3 RC2 20140218 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1272	1272	1272	1272	n/a
failures	n/a	34	44	36	30	n/a
fixed	n/a	n/a	n/a	n/a	n/a	n/a
NAB	n/a					n/a

1.6 M3 RC1 20140213 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1272	1272	1272		n/a
failures	n/a	34	44	36		n/a
fixed	n/a	n/a	n/a	n/a	n/a	n/a
NAB	n/a					n/a

1.6 M2 RC1 20140114 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1265	1265	1265	1265	n/a
failures	n/a	29	40	30	25	n/a
fixed	n/a	n/a	n/a	n/a	n/a	n/a
NAB	n/a					n/a

1.6 M1 RC1 20131203 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	n/a	1265	1265	1267	n/a
failures	n/a	n/a	37	30	25	n/a
fixed	n/a	n/a	n/a	n/a	n/a	n/a
NAB	n/a	n/a	37	30	25	n/a

1.5.1 RC2 20131213 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	n/a	1256	1256		n/a
failures	n/a	n/a	37	29		n/a
fixed	n/a	n/a	n/a	n/a		n/a
NAB	n/a	n/a	37	29		n/a

1.5 M5 RC6 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	n/a	1256	1256	1258	n/a
failures	n/a	n/a	40	28	21	n/a
fixed	n/a	n/a	n/a	n/a	n/a	n/a
NAB	n/a	n/a	40	28	21	n/a

1.5 M4 RC3 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	n/a	1256	1256	1258	n/a
failures	n/a	n/a	39	25	20	n/a
fixed	n/a	n/a	n/a	n/a	n/a	n/a
NAB	n/a	n/a	39	25	20	n/a

1.5 M4 RC2 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	n/a	1256	1256	1259	n/a
failures	n/a	n/a	40	25	20	n/a
fixed	n/a	n/a	n/a	n/a	n/a	n/a
NAB	n/a	n/a	40	25	20	n/a

1.5 M2 RC1 20130703 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	n/a	n/a	1256	1256	n/a
failures	n/a	n/a	n/a	25	20	n/a
fixed	n/a	n/a	n/a	0	0	n/a
NAB	n/a	n/a	n/a	25	20	n/a

1.4.1 RC1 20130612 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1232	1232	1232	1232	n/a
failures	n/a	23	36	19	21	n/a
fixed	n/a	0	0	0	0	n/a
NAB	n/a	23	36	19	21	n/a

1.5 M1 RC1 20130604 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1242	n/a	1242	1242	n/a
failures	n/a	28	n/a	23	19	n/a
fixed	n/a	0	n/a	0	0	n/a
NAB	n/a	28	n/a	23	19	n/a

1.3.2 20130516 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1232	1232	1232	1232	n/a
failures	n/a	23	42	18	24	n/a
fixed	n/a	0	0	0	0	n/a
NAB	n/a	23	42	18	24	n/a

1.4 M6 RC2 20130418 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1232	1232	1232	1232	n/a
failures	n/a	23	37	19	21	n/a
fixed	n/a	0	0	0	0	n/a
NAB	n/a	23	37	19	21	n/a

1.4 M5 RC3 20130327 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1238	n/a	1232	1250	n/a
failures	n/a	24	n/a	21	20	n/a
fixed	n/a	0	0	0	0	n/a
NAB	n/a	24	n/a	21	20	n/a

1.4 M5 RC2 20130327 build

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1232	1232	1232	1232	n/a
failures	n/a	24	36	19	20	n/a
fixed	n/a	0	0	0	0	n/a
NAB	n/a	24	36	19	20	n/a

1.4 M4 RC1 20130220 build

environment LTP version: ltp-full-20120903.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result.log -C result.fail -d /opt/ltp/tmp &> result.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1232	1232	1232	n/a	1232
failures	n/a	22	38	19	n/a	16
fixed	n/a	0	0	0	n/a	0
NAB	n/a	22	38	19	n/a	15

1.4 M3 RC2 20130131 build

environment LTP version: ltp-full-20120903.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result.log -C result.fail -d /opt/ltp/tmp &> result.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1232	1232	1232	n/a	1232
failures	n/a	24	40	23	n/a	17
fixed	n/a	0	0	0	n/a	0
NAB	n/a	24	40	23	n/a	17

1.4 M3 RC1 20130122 build

environment LTP version: ltp-full-20120903.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result.log -C result.fail -d /opt/ltp/tmp &> result.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1232	1232	1232	n/a	1232
failures	n/a	22	39	22	n/a	17
fixed	n/a	0	0	0	n/a	0
NAB	n/a	20	39	22	n/a	17

1.4 M1 RC1 20121128 build

environment LTP version: ltp-full-20120903.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result.log -C result.fail -d /opt/ltp/tmp &> result.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	n/a	1232	1232	1232	n/a	1232
failures	n/a	22	39	18	n/a	17
fixed	n/a	0	0	0	n/a	0
NAB	n/a	22	39	18	n/a	17

1.3 M5 RC4 20121010 build

environment LTP version: ltp-full-20120903.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result.log -C result.fail -d /opt/ltp/tmp &> result.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	1232	1232	1232	1232	n/a	1232
failures	21	22	38	18	n/a	16
fixed	0	0	0	0	n/a	0
NAB	21	22	38	18	n/a	16

1.3 M5 RC3 20121003 build

environment LTP version: ltp-full-20120903.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120926.log -C result-20120926.fail -d /opt/ltp/tmp &> result-20120926.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	1227	1232	1232	1232	n/a	1229
failures	26	22	39	18	n/a	17
fixed	0	0	0	0	n/a	0
NAB	26	21	39	18	n/a	17

1.3 M5 RC2 20120926 build

environment LTP version: ltp-full-20120903.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120926.log -C result-20120926.fail -d /opt/ltp/tmp &> result-20120926.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total		1232	1232	1232
failures		22	38	18
fixed		0	0	0
NAB		22	38	18

1.3 M4 RC3 20120916 build

environment LTP version: ltp-full-20120614.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120916.log -C result-20120916.fail -d /opt/ltp/tmp &> result-20120916.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total	1227	1229	1229	1229		1230
failures	7	23	40	20		15
fixed	0	0	0	0		0
NAB	7	23	40	20		15

1.3 M3 RC2 20120814 build

environment LTP version: ltp-full-20120614.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120814.log -C result-20120814.fail -d /opt/ltp/tmp &> result-20120814.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total		1229	1229	1229		1230
failures		23	33	21		17
fixed		0	0	0		0
NAB		23	33	21		17

1.3 20120801 build

environment LTP version: ltp-full-20120614.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120801.log -C result-20120801.fail -d /opt/ltp/tmp &> result-20120801.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay	huronriver
total		1229	1229	1229	1230	1235
failures		24	32	24	17	17
fixed		2	1	2	1	0
NAB		23	26	24	17	17

1.3 M2 RC1 20120712 build

environment LTP version: ltp-full-20120401.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120712.log -C result-20120712.fail -d /opt/ltp/tmp &> result-20120712.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total		1228	1228	n/a	1229
failures		26	32		18
fixed		8	8		0
NAB		21	24		15

1.1.2 20120630 build

environment LTP version: ltp-full-20120401.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120613.log -C result-20120613.fail -d /opt/ltp/tmp &> result-20120613.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total		1227	1228	1228	1229
failures		41	42	29	36
fixed		0	0	0	0
NAB		36	32	27	24

1.2.1 20120629 build

environment LTP version: ltp-full-20120401.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120613.log -C result-20120613.fail -d /opt/ltp/tmp &> result-20120613.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total		1228	1228	1228	1229
failures		23	30	22	19
fixed		0	0	0	0
NAB		21	24	20	16

1.3 M1 RC1 20120613 build

environment LTP version: ltp-full-20120401.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120613.log -C result-20120613.fail -d /opt/ltp/tmp &> result-20120613.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1229	1228	1227	1228	1227
failures	16	33	41	30	27
fixed	1	0	0	0	0
NAB	15	29	32	27	24

1.3 20120606 build

environment LTP version: ltp-full-20120401.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120606.log -C result-20120606.fail -d /opt/ltp/tmp &> result-20120606.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1229	1228	1227	1228	1227
failures	15	32	39	29	18
fixed	0	0	0	0	0
NAB	15	29	32	27	17

1.2 Denzil RC5

environment LTP version: ltp-full-20120401.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120423.log -C result-20120423.fail -d /opt/ltp/tmp &> result-20120423.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1229	1228	1228	1228	1227
failures	21	24	30	21	18
fixed	0	0	0	0	0
NAB	16	21	24	19	17

1.2 Denzil RC4

environment LTP version: ltp-full-20120401.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120418.log -C result-20120418.fail -d /opt/ltp/tmp &> result-20120418.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1229	1228	1228	1228	1227
failures	21	24	30	23	18
fixed	0	0	0	0	0
NAB	16	21	24	21	17

1.2 M4 RC3

environment LTP version: ltp-full-20120401.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120412.log -C result-20120412.fail -d /opt/ltp/tmp &> result-20120412.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1229	1228	n/a	1228	1227
failures	21	24	n/a	21	18
fixed	0	2	n/a	2	0
NAB	16	21	n/a	19	17

1.2 M4 RC2

environment LTP version: ltp-full-20120401.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120405.log -C result-20120405.fail -d /opt/ltp/tmp &> result-20120405.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1229	1206	1206	1206	1209
failures	21	22	28	20	17
fixed	0	0	0	0	1
NAB	16	20	21	19	16

1.2 M4 RC1

environment LTP version: ltp-full-20120104.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120328.log -C result-20120328.fail -d /opt/ltp/tmp &> result-20120328.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1208	1206	1206	1206	1206
failures	16	22	28	20	17
fixed	0	0	1	0	0
NAB	16	20	21	19	16

1.2 M3 RC1

environment LTP version: ltp-full-20120104.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120229.log -C result-20120229.fail -d /opt/ltp/tmp &> result-20120229.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1208	1206	1206	1206	1026
failures	16	22	29	20	17
fixed	11	11	10	11	11
NAB	13	20	21	19	16

1.1.1

environment LTP version: ltp-full-20110606.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-20120216.log -C result-20120216.fail -d /opt/ltp/tmp &> result-20120216.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1206	1206	1206	1203	1203
failures	36	41	43	41	36
fixed	0	0	0	0	0
NAB	22	36	36	39	24

1.2 M2 RC1

environment LTP version: ltp-full-20110915.bz2

profile: poky-image-sato-sdk

run command: ./runltp -p -l result-20120111.log -C result-20120111.fail -d /opt/ltp/tmp &> result-20120111.fulllog

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 "blacksand" to check detail data for that target

Status	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1206	1206	1207	1204	1206
failures	27	30	37	31	26
fixed	13	14	14	9	12
NAB	24	27	33	28	22

1.2 M1 RC2

environment LTP version: ltp-full-20110915.bz2

profile: poky-image-sato-sdk

run command: ./runltp -p -l result-20111213.log -C result-20111213.fail -d /opt/ltp/tmp &> result-20111213.fulllog

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 "qemuarm" to check detail data for that target

Status	Qemuppc	Qemuarm	Qemumips	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1102	1106	1102	1205	1206	1207	1204	1205
failures	34	35	33	36	39	40	38	34
fixed	0	0	0	1	0	0	0	1
NAB	33	34	31	36	34	32	36	34

1.0.2

environment LTP version: ltp-full-20110606.bz2

profile: poky-image-sato-sdk

run command: ./runltp -p -l result-20111201.log -C result-20111201.fail -d /opt/ltp/tmp &> result-20111201.fulllog

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 "qemuarm" to check detail data for that target

Status	Qemuppc	Qemuarm	Qemumips	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1104	1105	1104		1206	1206	1206
failures	35	35	35		36	137	36
fixed	0	0	0		0	0	0
NAB	34	35	35		36	37	36

1.1 M4 RC4

environment LTP version: ltp-full-20110606.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-M4-20110914.log -C result-M4-20110914.fail -d /opt/ltp/tmp &> result-M4-20110914.fulllog

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 "qemuarm" to check detail data for that target

Status	Qemuppc	Qemuarm	Qemumips	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1104	1105	1104	1208	1206	1206	1206	1208
failures	38	39	37	36	41	43	39	35
fixed	0	0	0	0	0	0	0	0
NAB	37	38	36	36	36	37	37	35

1.1 M4 RC3

environment LTP version: ltp-full-20110606.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-M4-20110914.log -C result-M4-20110914.fail -d /opt/ltp/tmp &> result-M4-20110914.fulllog

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 "qemuarm" to check detail data for that target

Status	Qemuppc	Qemuarm	Qemumips	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1104	1105	1104	1208	1206	1206	1206	1203
failures	37	38	37	37	41	44	39	37
fixed	1	1	0	0	2	16	0	0
NAB	37	38	36	37	36	37	37	37

1.1 M4 RC2

environment LTP version: ltp-full-20110606.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-M4-20110914.log -C result-M4-20110914.fail -d /opt/ltp/tmp &> result-M4-20110914.fulllog

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 "qemuarm" to check detail data for that target

Status	Qemuppc	Qemuarm	Qemumips	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1104	1105	1104	1180	1206	1206	1206	1180
failures	38	39	37	26	43	59	39	26
fixed	0	0	0	5	0	0	6	1
NAB	37	38	36	26	38	43	37	26

1.1 M3

environment LTP version: ltp-full-20110606.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-M3-20110806.log -C result-M3-20110806.fail -d /opt/ltp/tmp &> result-M3-20110806.fulllog

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 "qemuarm" to check detail data for that target

Status	Qemuppc	Qemuarm	Qemumips	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1104	1105	1104	1180	1207	1206	1206	1180
failures	35	37	36	28	41	57	42	27
fixed	0	3	3	0	3	104	0	9
NAB	34	36	32	23	35	51	36	27

1.1 M2

environment LTP version: ltp-full-20101031.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-M2-20110711.log -C result-M2-20110711.fail -d /opt/ltp/tmp &> result-M2-20110711.fulllog

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 "qemuarm" to check detail data for that target

Status	Qemuppc	Qemuarm	Qemumips	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1078	1078	1080	1182	1180	1179	1180	1180
failures	25	29	26	28	33	146	31	30
fixed	1	0	0	2	1	2	1	3
NAB	23	25	23	23	24	23	24	24

1.1 M1

environment LTP version: ltp-full-20101031.bz2

profile: core-image-sato-sdk

run command: ./runltp -p -l result-M1-20110528.log -C result-M1-20110528.fail -d /opt/ltp/tmp &> result-M2-20110528.fulllog

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 "qemuarm" to check detail data for that target

Status	Qemuppc	Qemuarm	Qemumips	blacksand	beagleboard	routerstation	mpc8315e-rdb	sugarbay
total	1078	1078	1078	1182	1180	1179	1180	1180
failures	26	29	26	30	34	146	32	33
fixed	0	0	0	0	0	0	0	0
NAB	23	25	23	4	25	23	25	0
LTP	0	0	0	0	0	0	0	0
Duplicated	0	0	0	29	5	5	5	35
pending	0	3	3	3	3	3	0	0

1.0 M4

environment LTP version: ltp-full-20101031.bz2

profile: poky-image-sdk

run command: ../runltp -p -l result-M4-20110318.log -C result-M4-20110318.fail -d /opt/tmp

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
NAB	26	1	1	4	1	2	1	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.

1.0 M2

environment LTP version: ltp-full-20101031.bz2

profile: poky-image-sdk

run command: ../runltp -p -q -l result-M2-20101218.log -C result-M2-20101218.fail -d /opt/tmp

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
total	1072	n/a	1071	1071	1081	n/a	n/a	1174	1182
failures	34	32	34	37	37	33	29	35	145 (*)
audit	100%	100%	100%	100%	100%	100%	100%	100%	0(0%)
fixed	6	0	0	1	0	0	0	0	0
NAB	26	1	1	4	1	2	1	0	0
LTP	2	2	0	0	1	0	0	0	0
Duplicated	0	29	33	29	29	31	28	35	0
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.