For LTP Test, some cases were a little unstable and random, with the 10/14 milestone build sdk image, the test case msgctl msgctl09 msgctl09) were blocked for hours(maybe forever). However if run one halt test case singly, it could be FAIL or PASS, not blocked. there are several similar testcases, such as getgid03 getgid03 getgid03_16 getgid03_16 getgroups03 getgroups03 getgroups03_16 getgroups03_16 setfsuid03 setfsuid03 setfsuid03_16 setfsuid03_16 setgid03 setgid03 setgid03_16 setgid03_16
this can't be reproduced recently. could you double-confirm?
If it doesn't re-occur in the next milestone test, we can close this
With RC1 20110226 buid and RC2 20110305 build, this can't be reproduced on qemuarm/mips/ppc. But on real hardware, some test cases will cause blocking: beagleboard(arm): waitid02 waitid02 routerstation(mips): mallocstress01 mallocstress mmapstress01 mmapstress01 -p 20 -t 0.2 routerstation only have 128MB memory and beagleboard have 256MB memory.
Any updates testing LTP on the HW targets?
With Yocto 1.1 M1 RC2 20110527 buid, this can't be reproduced on qemuarm/mips/ppc. On real hardware, some test cases will cause blocking: beagleboard(arm): waitid02 waitid02 This case can pass when run it individually. routerstation(mips): page01 page01 This case also can pass when run it individually.
So can we update the status of this bug since seems recent test the issue is gone?
With Yocto 1.2 M3 20120229 build, there is no cases blocking on real hardware with LTP 20120104. We could mark this bug as fixed.