This testcase check looks wrong. Failing to offline CPU X
does not mean that it failed to offline CPU 0.
Change the condition to check, that all but last CPU can
be offlined.
Signed-off-by: Jan Stancek <jstan...@redhat.com>
---
.../kernel/hotplug/cpu_hotplug/functional/cpuhotplug04.sh | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/testcases/kernel/hotplug/cpu_hotplug/functional/cpuhotplug04.sh
b/testcases/kernel/hotplug/cpu_hotplug/functional/cpuhotplug04.sh
index 6c9bb30..4fc6399 100755
--- a/testcases/kernel/hotplug/cpu_hotplug/functional/cpuhotplug04.sh
+++ b/testcases/kernel/hotplug/cpu_hotplug/functional/cpuhotplug04.sh
@@ -87,19 +87,22 @@ until [ $LOOP_COUNT -gt $HOTPLUG04_LOOPS ]; do
done
# Now offline all the CPUs
+ failed_to_offline=0
for i in $(get_present_cpus); do
if ! offline_cpu $i; then
- if [ "x$i" != "xcpu0" ]; then
- tst_resm TFAIL "Did not offline first CPU
(offlined $i instead)"
- tst_exit
- fi
+ tst_resm TINFO "Failed to offline $i"
+ failed_to_offline=$((failed_to_offline + 1))
fi
done
+ if [ "$failed_to_offline" -gt 1 ]; then
+ tst_resm TFAIL "$failed_to_offline CPUs failed to offline"
+ tst_exit
+ fi
LOOP_COUNT=$((LOOP_COUNT+1))
done
-tst_resm TPASS "Successfully offlined first CPU, $i"
+tst_resm TPASS "Successfully offlined all but last CPU"
tst_exit
--
1.8.3.1
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
