summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrea Grandi <agrandi@google.com>2022-12-09 12:04:40 -0800
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>2022-12-13 22:01:48 +0000
commit29d14affe55ffc3a2bb9eee19c355b756aeb7f7e (patch)
treef04d93afbece74013511588ae8963e0157e12e34
parent78eaccf378e8db32c4721f45e1325b1e06096313 (diff)
downloadchrome-ec-29d14affe55ffc3a2bb9eee19c355b756aeb7f7e.tar.gz
test: Increase tolerance of timer test
Timer test is flaky on hardware so we increase the tolerance to avoid false errors. This is okay since the primary goal of the test is to verify we can build timer functions on all platforms, not verify their accuracy. BUG=b:260723169 TEST=test/run_device_tests.py -b bloonchipper -t timer TEST=test/run_device_tests.py -b dartmonkey -t timer TEST=make run-timer BRANCH=none Signed-off-by: Andrea Grandi <agrandi@google.com> Change-Id: I0442fe212ce305b04ad89ba67e227abd6bcc7fa1 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/4093614 Code-Coverage: Zoss <zoss-cl-coverage@prod.google.com> Reviewed-by: Tom Hughes <tomhughes@chromium.org>
-rw-r--r--test/timer.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/timer.cc b/test/timer.cc
index 8eb5f87519..bac49f8498 100644
--- a/test/timer.cc
+++ b/test/timer.cc
@@ -26,7 +26,7 @@ test_static int test_usleep(void)
usleep(expected_duration);
int sleep_duration = time_since32(start_time);
- TEST_NEAR(expected_duration, sleep_duration, 20, "%d");
+ TEST_NEAR(expected_duration, sleep_duration, 100, "%d");
return EC_SUCCESS;
}