From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: jin.li@windriver.com
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 3/3] Fix cpuhotplug test case cpuhotplug05
Date: Wed, 14 Nov 2012 14:38:39 +0800 [thread overview]
Message-ID: <50A33C6F.1050604@cn.fujitsu.com> (raw)
In-Reply-To: <1352705641-27644-4-git-send-email-jin.li@windriver.com>
On 11/12/2012 03:34 PM, jin.li@windriver.com wrote:
> From: Jin Li <jin.li@windriver.com>
>
> Check whether sar is available befor run test
This is OK to me.
Thanks,
Wanlong Gao
>
> Signed-off-by: Jin Li <jin.li@windriver.com>
> ---
> testcases/kernel/hotplug/cpu_hotplug/functional/cpuhotplug05.sh | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/testcases/kernel/hotplug/cpu_hotplug/functional/cpuhotplug05.sh b/testcases/kernel/hotplug/cpu_hotplug/functional/cpuhotplug05.sh
> index ad57efe..e64b91c 100755
> --- a/testcases/kernel/hotplug/cpu_hotplug/functional/cpuhotplug05.sh
> +++ b/testcases/kernel/hotplug/cpu_hotplug/functional/cpuhotplug05.sh
> @@ -27,6 +27,11 @@ Desc: Does sar behave properly during CPU hotplug events?
>
> EOF
>
> +which sar > /dev/null 2>&1 || {
> + tst_resm TCONF "sar does not exist"
> + exit_clean 1
> +}
> +
> # Verify the specified CPU is available
> if ! cpu_is_valid "${CPU_TO_TEST}" ; then
> tst_resm TBROK"CPU${CPU_TO_TEST} not found"
>
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-11-14 6:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 7:33 [LTP] Fix cpuhotplug testcase cpuhotplug01 and cpuhotplug03 jin.li
2012-11-12 7:33 ` [LTP] [PATCH 1/3] Fix cpuhotplug test case cpuhotplug01 jin.li
2012-11-14 6:04 ` Wanlong Gao
2012-11-14 6:14 ` Li, Jin
2012-11-12 7:34 ` [LTP] [PATCH 2/3] Fix cpuhotplug test case cpuhotplug03 jin.li
2012-11-14 6:29 ` Wanlong Gao
2012-11-14 7:01 ` Li, Jin
2012-11-14 7:17 ` Wanlong Gao
2012-11-14 7:23 ` Li, Jin
2012-11-14 8:23 ` Wanlong Gao
2012-11-12 7:34 ` [LTP] [PATCH 3/3] Fix cpuhotplug test case cpuhotplug05 jin.li
2012-11-14 6:38 ` Wanlong Gao [this message]
2012-11-14 8:23 ` Wanlong Gao
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=50A33C6F.1050604@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=jin.li@windriver.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