From: Mason <slash.tmp@free.fr>
To: ltp@lists.linux.it
Subject: [LTP] Issue with the reporting of failed tests
Date: Thu, 21 Apr 2016 15:25:30 +0200 [thread overview]
Message-ID: <5718D4CA.5010607@free.fr> (raw)
Hello,
For a particular LTP run, I had 97 reported failures.
$ grep -c FAIL result-log.987
97
However, FAILCMDFILE contained 804 lines (with many duplicates).
$ wc -l result-failed.987
804 result-failed.987
$ sort result-failed.987 | uniq | wc -l
85
It seems some failures did not get recorded in FAILCMDFILE at all,
or were recorded, but later overwritten:
aio01, aio02, cgroup, controllers, ext4*, fs_racer, Numa-testcases
and some of the cron tests.
As discussed with metan on IRC, this has all the symptoms of a
FILE buffer shared between parent and child process. I am now
running LTP again with the following patch applied:
diff --git a/pan/ltp-pan.c b/pan/ltp-pan.c
index cee71aa3b587..44c026e88a47 100644
--- a/pan/ltp-pan.c
+++ b/pan/ltp-pan.c
@@ -535,6 +535,7 @@ int main(int argc, char **argv)
break;
}
+ fflush(failcmdfile);
cpid =
run_child(coll->ary[c], running + i, quiet_mode,
&failcnt, fmt_print, logfile);
When the run finishes, I will be able to tell if the issue
remains.
Regards.
next reply other threads:[~2016-04-21 13:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 13:25 Mason [this message]
2016-04-21 14:47 ` [LTP] Issue with the reporting of failed tests Mason
2016-04-21 15:30 ` Cyril Hrubis
2016-04-21 15:42 ` Mason
2016-04-21 17:02 ` Mason
2016-04-21 18:59 ` Mason
2016-04-22 13:29 ` Mason
2016-04-25 8:04 ` Mason
2016-04-25 11:40 ` Mason
2016-04-25 12:46 ` Mason
2016-04-25 13:31 ` Cyril Hrubis
2016-04-25 14:24 ` Mason
2016-04-25 14:46 ` Cyril Hrubis
2016-04-26 9:51 ` [LTP] getrusage04 on ARM fails sometimes Sebastian Frias
2016-04-25 13:04 ` [LTP] Issue with the reporting of failed tests Cyril Hrubis
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=5718D4CA.5010607@free.fr \
--to=slash.tmp@free.fr \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.