Bug 103187

Summary: [CI] igt@syncobj_wait@wait-[all|any]-interrupted - fail - Failed assertion: ret == -1 && errno == ETIME
Product: DRI Reporter: Marta Löfstedt <marta.lofstedt>
Component: IGTAssignee: Default DRI bug account <dri-devel>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: BXT, HSW, KBL, SNB i915 features:

Description Marta Löfstedt 2017-10-10 10:23:47 UTC 
On CI_DRM_3201 new tests igt@syncobj_wait@wait-[all|any]-interrupted failed on all shards:

(syncobj_wait:1606) CRITICAL: Test assertion failure function test_wait_interrupted, file syncobj_wait.c:736:
(syncobj_wait:1606) CRITICAL: Failed assertion: ret == -1 && errno == ETIME
Subtest wait-all-interrupted failed.

More data:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3201/shard-apl6/igt@syncobj_wait@wait-all-interrupted.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3201/shard-kbl2/igt@syncobj_wait@wait-all-interrupted.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3201/shard-hsw5/igt@syncobj_wait@wait-any-interrupted.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3201/shard-snb4/igt@syncobj_wait@wait-any-interrupted.html
Comment 1 Chris Wilson 2017-10-10 16:53:09 UTC 
Timeline is closed before testing; ergo it waits on a completed fence. Fixes are trivial.
Comment 2 Chris Wilson 2017-10-11 07:37:52 UTC 
commit eabe87de4652126480e2211d9c088a8eabea2c8a
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Tue Oct 10 18:13:41 2017 +0100

    igt/syncobj_wait: Close the sw_sync timeline after the test
    
    Closing the sw_sync timeline now signals any remaining fences upon it;
    but test_wait_interrupted requires the fence to be busy for the
    __syncobj_wait() not to immediately return with -ETIME (and so be
    interrupted instead).
Comment 3 Marta Löfstedt 2017-10-11 13:15:00 UTC 
Fix integrated in CI_DRM_3209 the tests are passing.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.