public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] open posix testsuite and names of testcases
Date: Thu, 06 Dec 2012 13:06:36 +0100	[thread overview]
Message-ID: <50C08A4C.1090402@redhat.com> (raw)

Hi,

this testsuite has many testcases, where binary name is in format: [number]-[number].run-test
This is not very helpful when trying to find out, which one actually
crashed or which one is responsible for kernel oops/hung tasks.
For example if I get in dmesg:
[  702.018706] 1-5.run-test[10140]: segfault at 7f84e724bed8 ip 0000000000402208 sp 00007f84e724bed0 error 6 in 1-5.run-test[400000+4000]
it's not clear, which testcase is responsible.

Does anyone have some ideas?

I had these two:
1. rename all testcases - lot of work, they are also referenced in some .sh scripts
2. modify run-tests.sh to copy it under more verbose name and run that one

diff --git a/testcases/open_posix_testsuite/bin/run-tests.sh b/testcases/open_posix_testsuite/bin/run-tests.sh
index bd8ca14..ddb6e0b 100755
--- a/testcases/open_posix_testsuite/bin/run-tests.sh
+++ b/testcases/open_posix_testsuite/bin/run-tests.sh
@@ -46,8 +46,11 @@ run_test() {
 
 	complog=$(basename $testname).log.$$
 
-	sh -c "$SCRIPT_DIR/t0 $TIMEOUT_VAL ./$1 $(cat ./$(echo "$1" | sed 's,\.[^\.]*,,').args 2>/dev/null)" > $complog 2>&1
+	# create a copy with more verbose name
+	new_testname=$(basename $TEST_PATH)-$1
+	cp -f ./$1 $new_testname
 
+	sh -c "$SCRIPT_DIR/t0 $TIMEOUT_VAL ./$new_testname $(cat ./$(echo "$1" | sed 's,\.[^\.]*,,').args 2>/dev/null)" > $complog 2>&1
 	ret_code=$?
 
 	if [ "$ret_code" = "0" ]; then

Which makes logs a bit more helpful:
[179468.329814] User process fault: interruption code 0x60011 in pthread_create-1-5.run-test[80000000+5000]

Regards,
Jan

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2012-12-06 12:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 12:06 Jan Stancek [this message]
2012-12-06 14:13 ` [LTP] open posix testsuite and names of testcases chrubis
     [not found]   ` <878595998.11610861.1354808151182.JavaMail.root@redhat.com>
2012-12-06 16:35     ` chrubis
2012-12-06 14:14 ` Wanlong Gao
2012-12-06 14:27   ` chrubis
2013-02-11 14:38 ` chrubis
     [not found]   ` <652016734.705678.1360596388811.JavaMail.root@redhat.com>
2013-02-11 15:51     ` chrubis
     [not found] <605746806.1323310.1360671766487.JavaMail.root@redhat.com>
     [not found] ` <51218CB1.8040709@cn.fujitsu.com>
2013-02-27 14:38   ` chrubis
2013-02-27 17:11     ` chrubis
2013-04-23 13:48       ` chrubis
     [not found]         ` <1822042882.3039242.1366879006975.JavaMail.root@redhat.com>
2013-04-25 10:42           ` chrubis

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=50C08A4C.1090402@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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