On Mon, 02 Jul 2007 12:28:50 +0530 Subrata Modak wrote:

quoted text
>   :-) *Dear All*,
>  
> *Note(s) from the Maintainer: *
> * We have seen that the LTP mailing lists has become active for the last 
> couple of months. Thanks to all who has made this happen. We as an 
> integrated team can work hard to make this Project a resounding success. 
> Following are the different milestones/activities that we aim to 
> perform/achieve in the coming months:
> 1) Investigation into LTP Log(s) Library to make this more meaningful 
> and parsible. Kindly provide your inputs for the output that LTP 
> generates now and whether/how you would like it to be in future

I don't know if this qualifies as an input for the output, but
I use a script to parse the results file to compute a gross/overall
"SCORE" value.  Instead of looking at lines that contain
"termination_id" (e.g.:
duration=0 termination_type=exited termination_id=0 corefile=no
), I look at the test results output format messages and count
them (ignoring the INFO lines) and then compute a SCORE based on
all of those lines.  Obviously that's why I've been changing several
test cases to use the standard test results output format.

ltprun-summary.sh is attached.  It uses prtag2tag.pl, which is also
attached.  (I also do this summary SCORE for the Open Posix Test suite.)

Example summary + SCORE:

Using logfile=/cruc/runs/1789/test_output/ltp.log
build errors:  0 lines
PASS:          2225
WARNing:       1
BROKen:        1
RETiRed:       0
FAIL:          0
CONFig error:  11
SCORE.ltp:        99.5


quoted text
> *Please also see the ChangeLog Below (June 2007):* *

so "[PATCH] float tests: use standard test results output"
(http://sourceforge.net/mailarchive/forum.php?thread_name=20070622214652.d137d055.rdunl...)
will be added next month?

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***