Re: [lsb-desktop] LSB runtime test failed in my system.
Wichmann, Mats D 写道:
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.
There are some information from the journal file, include all 19 tests.
10|823 /tset/LSB.os/ipc/semop/T.semop 13:27:07|TC Start, scenario ref 829-0
15|823 3.6-lite 19|TCM Start
400|823 1 1 13:27:07|IC Start
200|823 1 13:27:07|TP Start
520|823 1 00018785 2 1|path tracing error: path counter 0, expected 2
220|823 1 2 13:27:07|UNRESOLVED
410|823 1 1 13:27:07|IC End
400|823 2 1 13:27:07|IC Start
200|823 2 13:27:07|TP Start
520|823 2 00018785 2 1|path tracing error: path counter 0, expected 2
220|823 2 2 13:27:07|UNRESOLVED
410|823 2 1 13:27:07|IC End
400|823 3 1 13:27:07|IC Start
200|823 3 13:27:07|TP Start
520|823 3 00018785 1 1|path tracing error: path counter 1, expected 2
220|823 3 2 13:27:07|UNRESOLVED
410|823 3 1 13:27:07|IC End
400|823 4 1 13:27:07|IC Start
200|823 4 13:27:07|TP Start
520|823 4 00018785 1 1|setup: msgget(IPC_PRIVATE, 0666) unexpectedly
returned error: 28 (ENOSPC)
220|823 4 6 13:27:07|UNINITIATED
410|823 4 1 13:27:07|IC End
400|823 5 1 13:27:07|IC Start
200|823 5 13:27:07|TP Start
520|823 5 00018785 1 1|setup: msgget(IPC_PRIVATE, 0666) unexpectedly
returned error: 28 (ENOSPC)
220|823 5 6 13:27:07|UNINITIATED
410|823 5 1 13:27:07|IC End
400|823 6 1 13:27:07|IC Start
200|823 6 13:27:07|TP Start
520|823 6 00018785 2 1|path tracing error: path counter 1, expected 2
220|823 6 2 13:27:08|UNRESOLVED
410|823 6 1 13:27:08|IC End
400|823 7 1 13:27:08|IC Start
200|823 7 13:27:08|TP Start
520|823 7 00018785 1 1|setup: msgget(IPC_PRIVATE, 0666) unexpectedly
returned error: 28 (ENOSPC)
220|823 7 6 13:27:08|UNINITIATED
410|823 7 1 13:27:08|IC End
400|823 8 1 13:27:08|IC Start
200|823 8 13:27:08|TP Start
520|823 8 00018790 1 1|path tracing error: path counter 1, expected 3
220|823 8 2 13:27:08|UNRESOLVED
410|823 8 1 13:27:08|IC End
400|823 9 1 13:27:08|IC Start
200|823 9 13:27:08|TP Start
520|823 9 00018785 2 1|path tracing error: path counter 1, expected 3
220|823 9 2 13:27:08|UNRESOLVED
410|823 9 1 13:27:08|IC End
400|823 10 1 13:27:08|IC Start
200|823 10 13:27:08|TP Start
520|823 10 00018785 1 1|path tracing error: path counter 1, expected 2
220|823 10 2 13:27:08|UNRESOLVED
410|823 10 1 13:27:08|IC End
400|823 11 1 13:27:08|IC Start
200|823 11 13:27:08|TP Start
520|823 11 00018785 1 1|path tracing error: path counter 1, expected 2
220|823 11 2 13:27:08|UNRESOLVED
410|823 11 1 13:27:08|IC End
400|823 12 1 13:27:08|IC Start
200|823 12 13:27:08|TP Start
520|823 12 00018785 1 1|setup: msgget(IPC_PRIVATE, 0666) unexpectedly
returned error: 28 (ENOSPC)
220|823 12 6 13:27:08|UNINITIATED
410|823 12 1 13:27:08|IC End
400|823 13 1 13:27:08|IC Start
200|823 13 13:27:08|TP Start
520|823 13 00018785 1 1|setup: msgget(IPC_PRIVATE, 0666) unexpectedly
returned error: 28 (ENOSPC)
220|823 13 6 13:27:08|UNINITIATED
410|823 13 1 13:27:08|IC End
400|823 14 1 13:27:08|IC Start
200|823 14 13:27:08|TP Start
220|823 14 7 13:27:08|NORESULT
410|823 14 1 13:27:08|IC End
400|823 15 1 13:27:08|IC Start
200|823 15 13:27:08|TP Start
520|823 15 00018785 1 1|setup: msgget(IPC_PRIVATE, 0666) unexpectedly
returned error: 28 (ENOSPC)
220|823 15 6 13:27:08|UNINITIATED
410|823 15 1 13:27:08|IC End
400|823 16 1 13:27:08|IC Start
200|823 16 13:27:08|TP Start
520|823 16 00018785 1 1|path tracing error: path counter 0, expected 1
220|823 16 2 13:27:08|UNRESOLVED
410|823 16 1 13:27:08|IC End
400|823 17 1 13:27:08|IC Start
200|823 17 13:27:08|TP Start
520|823 17 00018785 1 1|path tracing error: path counter 0, expected 1
220|823 17 2 13:27:08|UNRESOLVED
410|823 17 1 13:27:08|IC End
400|823 18 1 13:27:08|IC Start
200|823 18 13:27:08|TP Start
520|823 18 00018785 1 1|path tracing error: path counter 0, expected 1
220|823 18 2 13:27:08|UNRESOLVED
410|823 18 1 13:27:08|IC End
400|823 19 1 13:27:08|IC Start
200|823 19 13:27:08|TP Start
520|823 19 00018785 1 1|path tracing error: path counter 0, expected 1
220|823 19 2 13:27:08|UNRESOLVED
410|823 19 1 13:27:08|IC End
80|823 0 13:27:08|TC End, scenario ref 829-0
-- mats
thanks.
Wingsun
begin:vcard
fn:Wing Sun
n:Sun;Wing
email;internet:chunyang.sun@sw-linux.com
tel;work:(8625)83191923-188
tel;fax:(8625)83190921
version:2.1
end:vcard
Reply to: