[Bug 102650] New: [CI][ALL] Failure waiting on unsignaled fence on closed timeline

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 102650
           Summary: [CI][ALL] Failure waiting on unsignaled fence on
                    closed timeline
           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

On CI_DRM_3064, the all the machines running igt at sw_sync@timeline_closed
started failing the test with the following error message:

(sw_sync:1591) CRITICAL: Test assertion failure function test_timeline_closed,
file sw_sync.c:86:
(sw_sync:1591) CRITICAL: Failed assertion: sync_fence_wait(fence, 0) == -ETIME
(sw_sync:1591) CRITICAL: Last errno: 2, No such file or directory
(sw_sync:1591) CRITICAL: Failure waiting on unsignaled fence on closed timeline

It appears to be due to [1] since there were no IGT changes and this is the
only line in commits_short.

[1] ea4d5a270b57 dma-buf/sw_sync: force signal all unsignaled fences on dying
timeline 

Full logs:
 -
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3064/shard-snb5/igt@sw_sync@timeline_closed.html
 -
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3064/shard-hsw4/igt@sw_sync@timeline_closed.html
 -
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3064/shard-apl6/igt@sw_sync@timeline_closed.html
 -
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3064/shard-kbl3/igt@sw_sync@timeline_closed.html

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