From: chrubis@suse.cz
To: Xing Gu <gux.fnst@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v3 2/2] hotplug/cpu_hotplug: add it to run default and cleanup
Date: Tue, 2 Sep 2014 15:01:08 +0200 [thread overview]
Message-ID: <20140902130108.GA7361@rei.suse.cz> (raw)
In-Reply-To: <1404291667-13198-2-git-send-email-gux.fnst@cn.fujitsu.com>
Hi!
> Add cpu_hotplug tests to scenario_groups/default.
Pushed without the addition to the scenario_groups/default.
On single cpu machine most of the testcases fails with:
cpuhotplug05 1 TBROK : CPU1 not found
or with:
cat: /sys/devices/system/cpu/cpu1/online: No such file or directory
/opt/ltp/testcases/bin/cpuhotplug_hotplug.sh: line 198: [: =: unary
operator exp
cpuhotplug07 1 TBROK : CPU1 cannot be onlined
The testcases should exit properly with TCONF in this case. I know that
single cpu machines are not that common today, but we should we should
work correctly even on these. Let's add it to the default run once this
is fixed.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-09-02 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 12:31 [LTP] [PATCH] hotplug/cpu_hotplug: add it to run default and cleanup Xing Gu
2014-06-12 12:10 ` chrubis
2014-06-20 9:30 ` [LTP] [PATCH v2] " Xing Gu
2014-06-26 12:51 ` chrubis
2014-07-02 9:01 ` [LTP] [PATCH v3 1/2] hotplug/cpu_hotplug: rename files in include and tools directories Xing Gu
2014-07-02 9:01 ` [LTP] [PATCH v3 2/2] hotplug/cpu_hotplug: add it to run default and cleanup Xing Gu
2014-09-02 13:01 ` chrubis [this message]
2014-08-19 2:57 ` [LTP] [PATCH v3 1/2] hotplug/cpu_hotplug: rename files in include and tools directories gux.fnst
2014-08-19 12:53 ` 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=20140902130108.GA7361@rei.suse.cz \
--to=chrubis@suse.cz \
--cc=gux.fnst@cn.fujitsu.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