RE: merged dejagnu testsuites

["Stone, Joshua I" <joshua dot i dot stone at intel dot com>]

On Tuesday, August 29, 2006 9:05 AM, Frank Ch. Eigler wrote:
> You probably mean the new pass1-4/*.exp files.  Only a few weeks went
> by, but already I don't recall why the ">>& systemtap.log" is there
> :-). It wasn't intentional to lose the *ko error messages.

Yes I mean the pass1-4, but I'm actually worried about losing the
messages from *ok failures.

Before I wasn't waiting until the end of the testsuite run -- I waited
until I saw a failure and then hit crtl-c and looked at the logfile.

Now I see that when you let the testsuite run through completely, some
output ends up at the end of the file.  It's not all that useful though
-- I see a deluge of information from what appears to be both passing
and failing tests, with no clear way to tell what output came from what
test.  A 7MB log file is far too verbose for me to figure out what
happened.  It seems to be giving be something like this:

	Running [...]/buildok/foo.stp
	PASS: buildok/foo.stp
	Running [...]/buildok/bar.stp
	FAIL: buildok/bar.stp
	Running [...]/buildok/baz.stp
	PASS: buildok/baz.stp
	[foo's output]
	[bar's output]
	[baz's output]

I'm not even sure if all that output at the end really has the error
information I need.  For example, buildok/syscall.stp is failing (known
problem -- missing some syscalls), but I can't find anything in the log
file that tells me the failure message.

The deluge wouldn't be so bad if it was kept inline with the test
status, i.e.,

	Running [...]/buildok/foo.stp
	[foo's output]
	PASS: buildok/foo.stp
	Running [...]/buildok/bar.stp
	[bar's output]
	FAIL: buildok/bar.stp
	Running [...]/buildok/baz.stp
	[baz's output]
	PASS: buildok/baz.stp


I tried taking out your mysterious ">>& systemtap.log", and that just
made it so I don't see the output in the log at all.  So to refresh your
memory, Frank, you probably added that so the output would not be
completely lost.  ;)


Josh