From: chrubis@suse.cz
To: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
Cc: LTP <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] How to get detailed system information between running tests
Date: Tue, 13 May 2014 14:11:23 +0200 [thread overview]
Message-ID: <20140513121123.GD12144@rei> (raw)
In-Reply-To: <53720837.8010805@cn.fujitsu.com>
Hi,
> Recently I met some fails in RHEL7.0Beta by running "./runltp", the fails are below:
> ------------------------------------------
> hugemmap01 FAIL 2
> hugemmap03 FAIL 2
> hugemmap04 FAIL 2
> ------------------------------------------
> After some investigation, I found that it is "echo 128 > /proc/sys/vm/nr_hugepages" causing
> these fails. By catting /proc/buddyinfo or catting /proc/pagetypeinfo, I found that the system
> has too many memory fragments and was not able to allocate 128 hugepages. So I also want
> to know which test cases results in these too many memory fragments.
>
> It seems that LTP does not provide a method to get the system's status information between these
> tests. I think we may add patches to support providing a shell script to ltp-pan, which will be called before
> and after every test case, to record some system status information. In this shell script, you can collect
> system information you has interests in, then save these information to files. Then we can analysis these
> files to know which case causing the big system status changes.
>
> Anybody has some better ideas, thanks.
That sounds more like a job for MMTests[1]. The upside of MMTests is
that all the scripts for collection system information are allready
written along with exporters to html and comparsion tools. The downside
is that there is not much of documentation and LTP support is untested.
[1] https://github.com/gormanm/mmtests
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
parent reply other threads:[~2014-05-13 12:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <53720837.8010805@cn.fujitsu.com>]
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=20140513121123.GD12144@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=wangxg.fnst@cn.fujitsu.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