[Bug 107500] New: [CI][SHARDS] igt at gem_eio@reset-stress - fail - Failed assertion: elapsed < 250e6

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=107500

            Bug ID: 107500
           Summary: [CI][SHARDS] igt at gem_eio@reset-stress - fail - Failed
                    assertion: elapsed < 250e6
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: martin.peres at free.fr
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4587/shard-hsw2/igt@gem_eio@reset-stress.html

(gem_eio:2635) CRITICAL: Test assertion failure function check_wait, file
../tests/gem_eio.c:258:
(gem_eio:2635) CRITICAL: Failed assertion: elapsed < 250e6
(gem_eio:2635) CRITICAL: Wake up following reset+wedge took 3723.972ms
Subtest reset-stress failed.

Introduced by: 

igt/gem_eio: Measure reset delay from thread

We assert that we complete a wedge within 250ms. However, when we use a
thread to delay the wedging until after we start waiting, that thread
itself is delayed longer than our wait timeout. This results in a false
positive error where we fail the test before we even trigger the reset.

Reorder the test so that we only ever measure the delay from triggering
the reset until we wakeup, and assert that is in a timely fashion
(less than 250ms).

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105954
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180806/bfe0c443/attachment.html>