[strace/strace] Rewrite time-sensitive checks to compare test's time notion with strace's (#182)

[esyr]

sleep/nanosleep/-r/-t/-T/delay/syscall stats checks rely on the fact that the nanosleep call (or its equivalents) wakes up the process within some tolerance, usually 0.1—0.2 seconds. This is not the case in some virtualised environments with heavy over-provisioning, one notable example is s390, which results in test failures which are not indicative of strace's issues (but rather some intermittent issues with the environment).

One possible fix for this is to collect the experienced delay from the test program's PoV and compare it to strace's notion of the time passed.

Via https://lists.strace.io/pipermail/strace-devel/2021-April/010501.html

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/strace/strace/issues/182
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20210407/0cc1bc38/attachment.htm>