[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: [lsb-desktop] LSB runtime test failed in my system.



>I run LSB 3.1 test on my system - a debian like system. I got some
>failed information from runtime test result:
>Warning, wget was unable to locate network waivers to retrieve..
>/tset/LSB.os/ipc/semop/T.semop 1 UNRESOLVED
>/tset/LSB.os/ipc/semop/T.semop 2 UNRESOLVED
>/tset/LSB.os/ipc/semop/T.semop 3 UNRESOLVED
>/tset/LSB.os/ipc/semop/T.semop 4 UNINITIATED
>/tset/LSB.os/ipc/semop/T.semop 5 UNINITIATED
>/tset/LSB.os/ipc/semop/T.semop 6 UNRESOLVED
>/tset/LSB.os/ipc/semop/T.semop 7 UNINITIATED
>/tset/LSB.os/ipc/semop/T.semop 8 UNRESOLVED
>/tset/LSB.os/ipc/semop/T.semop 9 UNRESOLVED
>/tset/LSB.os/ipc/semop/T.semop 10 UNRESOLVED
>/tset/LSB.os/ipc/semop/T.semop 11 UNRESOLVED
>/tset/LSB.os/ipc/semop/T.semop 12 UNINITIATED
>/tset/LSB.os/ipc/semop/T.semop 13 UNINITIATED
>/tset/LSB.os/ipc/semop/T.semop 14 UNREPORTED
>/tset/LSB.os/ipc/semop/T.semop 15 UNINITIATED
>/tset/LSB.os/ipc/semop/T.semop 16 UNRESOLVED
>/tset/LSB.os/ipc/semop/T.semop 17 UNRESOLVED
>/tset/LSB.os/ipc/semop/T.semop 18 UNRESOLVED
>/tset/LSB.os/ipc/semop/T.semop 19 UNRESOLVED

>Total Tests Failed (including waived): 19

Don't have anything terribly helpful to say, really. This is 
not a problem I've ever seen or heard of anyone else seeing.
The good news is that this is your only failure area, and
usually when all the tests in an area fail like this it's a
single problem, often a setup problem, and clearing that will
make all or most of them go away.

All of these tests are either unresolved or uninitated, not
fail, which usually means the tests are not running - 
uninitated means it didn't start at all, usually because some
key condition is not met.  uresolved means you didn't get a
clean error result, usually because the test quit (via
segfault or some similar fatal error condition). One would
guess that semaphores are not available to the tests for
some reason, possibly setup, possibly kernel build, etc.

It may help us recognize something if you post a snippet from
the journal file, either all nineteen tests or if you want
to keep it short just the first five (which would include
a couple of each failure more).  It's not guaranteed that
any useful information ended up in the journal, but it's
always the next step when seeing failures to look at the
detailed information in the journal, sometimes in concert
with the test sources.

-- mats
 



Reply to: