From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] log per test?
Date: Fri, 26 Jan 2018 12:07:51 +0100 [thread overview]
Message-ID: <20180126110750.GA2391@rei> (raw)
In-Reply-To: <20180125172716.o5aioq4htmloksa5@xps>
Hi!
> I'm looking at how we run LTP at Linaro and currently we redirect all
> output to a file. When a test fails, someone has to read through the log
> to find the test failure. Not difficult, but in terms of automation,
> we'd like to be able to post just the log of the test that failed
> directly. We're starting to work on parsing it, but that too can be a
> little tricky.
>
> I noticed runltp -K to capture dmesg output per test - very useful!
>
> Is there anything similar for capturing stdout and stderr per test? I
> saw some facilities in ltp-pan but I didn't see anything in runltp
> (though I may have missed it). I'm not sure if what I'm asking for
> already exists, or if I'd have to write a new i.e. reporttype.
As far as I know there is none. And the code that runs the testcases is
quite dated and was in maintenance mode for quite some time.
Which is the reason why I started to work on a replacement recently with
more modular approach in mind so that it can run open posix testcases as
well and also export results in various formats so that it can be
plugged into automation frameworks with minimal effort. It's not
finished yet, but it kind of works at this point, you can have a look at
it at:
https://github.com/metan-ucw/ltp/tree/master/tools/runltp-ng
And as usual comments and patches are welcomed :-).
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2018-01-26 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 17:27 [LTP] log per test? Dan Rue
2018-01-26 11:07 ` Cyril Hrubis [this message]
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=20180126110750.GA2391@rei \
--to=chrubis@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox