summaryrefslogtreecommitdiff
path: root/support/timespec.h
diff options
context:
space:
mode:
authorLucas A. M. Magalhaes <lamm@linux.ibm.com>2020-07-10 19:41:06 -0300
committerTulio Magno Quites Machado Filho <tuliom@linux.ibm.com>2020-07-10 19:41:06 -0300
commit04deeaa9ea74b0679dfc9d9155a37b6425f19a9f (patch)
tree1c45c61f362a93a31f919fe2d428898720b59e1d /support/timespec.h
parent7c7bcf3634e44cf7e001aaa302138c1ee0e58f8c (diff)
downloadglibc-04deeaa9ea74b0679dfc9d9155a37b6425f19a9f.tar.gz
Fix time/tst-cpuclock1 intermitent failures
This test fails intermittently in systems with heavy load as CLOCK_PROCESS_CPUTIME_ID is subject to scheduler pressure. Thus the test boundaries were relaxed to keep it from failing on such systems. A refactor of the spent time checking was made with some support functions. With the advantage to representing time jitter in percent of the target. The values used by the test boundaries are all empirical. Reviewed-by: Carlos O'Donell <carlos@redhat.com>
Diffstat (limited to 'support/timespec.h')
-rw-r--r--support/timespec.h8
1 files changed, 8 insertions, 0 deletions
diff --git a/support/timespec.h b/support/timespec.h
index c5852dfe75..fd5466745d 100644
--- a/support/timespec.h
+++ b/support/timespec.h
@@ -48,6 +48,14 @@ void test_timespec_equal_or_after_impl (const char *file, int line,
const struct timespec left,
const struct timespec right);
+long support_timespec_ns (struct timespec time);
+
+struct timespec support_timespec_normalize (struct timespec time);
+
+int support_timespec_check_in_range (struct timespec expected, struct timespec observed,
+ double lower_bound, double upper_bound);
+
+
/* Check that the timespec on the left represents a time before the
time on the right. */
#define TEST_TIMESPEC_BEFORE(left, right) \