weird result: sigconcept 41 UNRES (sometimes)

"Wichmann, Mats D" <[email protected]>
Newsgroups gmane.linux.lsb.test-suite
Message-ID <A06801158AE07847B27A52C1A074BC1D08448FB2@fmsmsx404.amr.corp.intel.com>
The sigconcept 41 test sometimes goes unresolved.
Does anyone know what this is?  I don't find any
current records of an analysis on the website, but
in googling I notice this has cropped up in various
journals for a long time - I see mentions of tests
on Debian that saw this (LSB 2 testing) back in '03,
we see it in the lsbsi for both LSB 2 and LSB 3, 
it's on the wiki as an unalayzed result in several 
configurations.

It doesn't seem to always occur, my own memory is
that I've had the fail on a specific machine/config
and rerun the test and not seen it, and vice versa
so it's possibly transient.  The lsbsi results record
it as only happening on /some/ architectures, but
other results also record only /some/ but a different
set, so I think this is another indiciation of the 
unpredictability, not arch-specific issues.

Anybody have anything useful to share?  Something
we concluded, didn't write down, and I've forgotten?

When this happens, the journal records the testcase
was sent a signal which should have stopped it,
but did not. When the problem happens, it always
looks like the journal snip recorded in the
wiki page:

http://www.linuxbase.org/LSBWiki/LsbRuntimeTest3

and reproduced here:

10|531 /tset/POSIX.os/procprim/sigconcept/T.sigconcept 10:20:25|TC
Start, scenario ref 534-0
...
400|531 41 1 10:42:29|IC Start
200|531 41 10:42:29|TP Start
520|531 41 00014023 2 1|child process terminated incorrectly
520|531 41 00014023 2 2|expected action: process terminated - signal 9
520|531 41 00014023 2 3|observed action: process still active
520|531 41 00014547 1 1|unexpected signal 15 (SIGTERM) received
520|531 41 00014023 4 1|child process terminated incorrectly
520|531 41 00014023 4 2|expected action: process terminated - signal 9
520|531 41 00014023 4 3|observed action: process still active
520|531 41 00014551 1 1|unexpected signal 15 (SIGTERM) received
520|531 41 00014023 5 1|path tracing error: path counter 3, expected 5
220|531 41 2 10:42:57|UNRESOLVED
410|531 41 1 10:42:57|IC End
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.