Bug 103188

Summary:	[CI] igt@syncobj_wait@wait-[any\|for-submit]-snapshot - fail - Failed assertion: wait.wait.first_signaled == 1
Product:	DRI	Reporter:	Marta Löfstedt <marta.lofstedt>
Component:	IGT	Assignee:	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:29:36 UTC

New tests igt@syncobj_wait@wait-[any|for-submit]-snapshot failed on CI_DRM_3201 for all shards:

(syncobj_wait:1597) CRITICAL: Test assertion failure function test_wait_snapshot, file syncobj_wait.c:588:
(syncobj_wait:1597) CRITICAL: Failed assertion: wait.wait.first_signaled == 1
(syncobj_wait:1597) CRITICAL: error: 0 != 1
Subtest wait-for-submit-snapshot failed.


https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3201/shard-apl8/igt@syncobj_wait@wait-any-snapshot.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3201/shard-kbl3/igt@syncobj_wait@wait-any-snapshot.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3201/shard-hsw6/igt@syncobj_wait@wait-for-submit-snapshot.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3201/shard-snb5/igt@syncobj_wait@wait-for-submit-snapshot.html

Comment 1 Jani Saarinen 2017-10-11 05:48:32 UTC

Patch reference: https://patchwork.freedesktop.org/series/31678/

Comment 2 Chris Wilson 2017-10-11 07:37:27 UTC

commit 136100c2f00b590bc9485100cce012282c1217cf (HEAD, upstream/master)
Author: Jason Ekstrand <jason@jlekstrand.net>
Date:   Tue Oct 10 13:02:20 2017 -0700

    igt/syncobj_wait: Don't close the timeline early in wait_snapshot
    
    Closing the sw_sync timeline now signals any remaining fences upon it;
    but test_wait_snapshot requires the fence to continue to be busy so that
    the __syncobj_wait() will return with -ETIME.

Comment 3 Marta Löfstedt 2017-10-11 13:14:39 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.