From 931bbc51339047382f91397a4cb5fe2f94c6cd36 Mon Sep 17 00:00:00 2001 From: Javi Merino <javi.merino@arm.com> Date: Thu, 11 Feb 2016 15:33:47 +0000 Subject: [PATCH] test/eas/rfc: fix calculation of the first period of the task We avoid the first period of the rtapp task in the boosted utilization signal test because of the initial high load. The period we read from the parameters is expressed in milliseconds but the index of the dataframes returned by trappy is in seconds. Convert rtapp_period to seconds before adding it to task_start to correctly add the two variables in the same unit (seconds). --- tests/stune/smoke_test_ramp.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/stune/smoke_test_ramp.py b/tests/stune/smoke_test_ramp.py index 7ab1bc0b8..e7a9d9eb3 100644 --- a/tests/stune/smoke_test_ramp.py +++ b/tests/stune/smoke_test_ramp.py @@ -61,7 +61,7 @@ class STune(LisaTest): # high load and it overutilizes the CPU rtapp_period = first_task_params[first_task_name]["params"]["period_ms"] task_start = boost_task_rtapp.index[0] - after_first_period = task_start + rtapp_period + after_first_period = task_start + (rtapp_period / 1000.) boost_task_rtapp = boost_task_rtapp.ix[after_first_period:] sched_load_scale = 1024 -- GitLab