Commit a6696d7f authored by Krzysztof Goreczny's avatar Krzysztof Goreczny Committed by Konrad Sztyber
Browse files

test: make reactor_is_busy_or_idle() less restrictive 



Extensive interrupt mode testing shows that reactor CPU load as reported
by the top in reactor_is_busy_or_idle during traffic fluctuates between
50 and 80%, 66.7% is reported quite often. With 10s time slot it happens
that all readings are 66.7% or less.
To avoid false positives in CI and not make the test any longer than it
already is lower the arbitrary chosen value o 70% to 65% as an
indication that the CPU is indeed busy.

Change-Id: I4946ab2fc0b0704ef6e3d6905cfcae6331e8ec9c
Signed-off-by: default avatarKrzysztof Goreczny <krzysztof.goreczny@dell.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/24596


Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: default avatarKonrad Sztyber <konrad.sztyber@intel.com>
Reviewed-by: default avatarJim Harris <jim.harris@samsung.com>
parent 2de3092a

test/interrupt/common.sh

+1 −1
Original line number Diff line number Diff line
@@ -25,7 +25,7 @@ function reactor_is_busy_or_idle() { 
		cpu_rate=$(echo $top_reactor | sed -e 's/^\s*//g' | awk '{print $9}')

		cpu_rate=${cpu_rate%.*}



		if [[ $state = "busy" ]] && [[ $cpu_rate -lt 70 ]]; then

		if [[ $state = "busy" ]] && [[ $cpu_rate -lt 65 ]]; then

			sleep 1

		elif [[ $state = "idle" ]] && [[ $cpu_rate -gt 30 ]]; then

			sleep 1