mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Subrata Modak <subrata@linux.vnet.ibm.com>
Cc: ltp-list@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	ltp-announce@lists.sourceforge.net
Subject: Re: [LTP] [ANNOUNCE] The Linux Test Project has been Released for June 2007,
Date: Mon, 2 Jul 2007 08:50:54 -0700	[thread overview]
Message-ID: <20070702085054.0efb79ff.rdunlap@xenotime.net> (raw)
In-Reply-To: <4688A22A.2090907@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]

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

>   :-) *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


> *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.rdunlap%40xenotime.net&forum_name=ltp-list)
will be added next month?

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

[-- Attachment #2: ltprun-summary.sh --]
[-- Type: application/x-shellscript, Size: 1554 bytes --]

[-- Attachment #3: prtag2tag.pl --]
[-- Type: application/x-perl, Size: 744 bytes --]

       reply	other threads:[~2007-07-02 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4688A22A.2090907@linux.vnet.ibm.com>
2007-07-02 15:50 ` Randy Dunlap [this message]
2007-09-18 11:51   ` [LTP] Validating exact PASS and FAIL scenarios for LTP Subrata Modak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070702085054.0efb79ff.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-announce@lists.sourceforge.net \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=subrata@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®