[Bug 111925] New: [CI][SHARDS]igt at gem_eio@in-flight-contexts-immediate|igt at gem_eio@in-flight-contexts-10ms - fail - Failed assertion: igt_seconds_elapsed(&ts) <= 10

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 111925
           Summary: [CI][SHARDS]igt at gem_eio@in-flight-contexts-immediate|i
                    gt at gem_eio@in-flight-contexts-10ms - fail - Failed
                    assertion: igt_seconds_elapsed(&ts) <= 10
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: not set
          Priority: not set
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: lakshminarayana.vudum at intel.com
        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/CI_DRM_7012/shard-hsw4/igt@gem_eio@in-flight-contexts-10ms.html
Starting subtest: in-flight-contexts-10ms
(gem_eio:1508) CRITICAL: Test assertion failure function trigger_reset, file
../tests/i915/gem_eio.c:85:
(gem_eio:1508) CRITICAL: Failed assertion: igt_seconds_elapsed(&ts) <= 10
(gem_eio:1508) CRITICAL: error: 26 > 10
Subtest in-flight-contexts-10ms failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7011/shard-snb7/igt@gem_eio@in-flight-contexts-immediate.html
Starting subtest: in-flight-contexts-immediate
(gem_eio:3011) CRITICAL: Test assertion failure function trigger_reset, file
../tests/i915/gem_eio.c:85:
(gem_eio:3011) CRITICAL: Failed assertion: igt_seconds_elapsed(&ts) <= 10
(gem_eio:3011) CRITICAL: error: 39 > 10
Subtest in-flight-contexts-immediate failed.

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