[PATCH i-g-t v1 0/1] runner: Use BOOTTIME for time checks

[Kamil Konieczny]

Instead of using igt_gettime() function, use local runner function
with CLOCK_BOOTTIME, which counts in also suspend time.

You could look into this here:

https://intel-gfx-ci.01.org/tree/intel-xe/xe-2730-873b1a50bb4394e95332cfa611aa6463de6b7cb0/shard-bmg-7/igt_runner14.txt

search for 2x-flip-vs-suspend and see difference:

[77.376851] [020/123] (932s left) kms_flip (2x-flip-vs-suspend)

[305.147183] Subtest 2x-flip-vs-suspend: SUCCESS (40.168s)
[314.469660] [021/123] (891s left) kms_addfb_basic (bad-pitch-999)

This shows test runs for around 932 - 891 = 40 seconds, while wall
time shows it took around 305 - 77 = 228 seconds, so it should had
less then 704s left.

Separate issue seen from this log is 9s difference until
next test run.

Link for igt_runner14.txt is available here:

https://intel-gfx-ci.01.org/tree/intel-xe/xe-2730-873b1a50bb4394e95332cfa611aa6463de6b7cb0/shard-bmg-7/igt@xe_pmu@engine-activity-idle@engine-drm_xe_engine_class_video_decode0.html

Cc: Ewelina Musial <ewelina.musial at intel.com>
Cc: Karol Krol <karol.krol at intel.com>
Cc: Petri Latvala <adrinael at adrinael.net>

Kamil Konieczny (1):
  runner/executor: Use bootime for time checks

 runner/executor.c | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

-- 
2.49.0