This issue started on CI_DRM_3129 and has, so far been reproduced on CI_DRM_3130, CI_DRM_3131 (gem_exec_schedule:2582) CRITICAL: Test assertion failure function ctx_set_priority, file gem_exec_schedule.c:64: (gem_exec_schedule:2582) CRITICAL: Failed assertion: __ctx_set_priority(fd, ctx, prio) == 0 (gem_exec_schedule:2582) CRITICAL: Last errno: 22, Invalid argument (gem_exec_schedule:2582) CRITICAL: error: -22 != 0 Subtest fifo-blt failed. Some full data links: igt@gem_exec_schedule@fifo-blt: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3129/shard-snb3/igt@gem_exec_schedule@fifo-blt.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3129/shard-hsw2/igt@gem_exec_schedule@fifo-blt.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3129/shard-apl5/igt@gem_exec_schedule@fifo-blt.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3129/shard-kbl2/igt@gem_exec_schedule@fifo-blt.html igt@gem_exec_schedule@fifo-bsd: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3129/shard-hsw5/igt@gem_exec_schedule@fifo-bsd.html igt@gem_exec_schedule@fifo-bsd1: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3129/shard-kbl3/igt@gem_exec_schedule@fifo-bsd1.html igt@gem_exec_schedule@fifo-bsd2: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3129/shard-kbl4/igt@gem_exec_schedule@fifo-bsd2.html igt@gem_exec_schedule@fifo-render: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3129/shard-snb3/igt@gem_exec_schedule@fifo-render.html igt@gem_exec_schedule@fifo-vebox: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3129/shard-hsw2/igt@gem_exec_schedule@fifo-vebox.html
https://patchwork.freedesktop.org/series/30834/ https://patchwork.freedesktop.org/series/30855/
commit 2885b10f99b4beeb046e75af8b8488c229f629d3 (upstream/master, origin/master, origin/HEAD) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Sep 25 20:59:54 2017 +0100 igt/gem_exec_schedule: Ignore set-priority failures on old kernels When plugging the device, we need to submit batches at highest priority so that they cannot be gazumped by the queued requests. On older kernels that do not support the user changing context priority, all contexts therefore have the same default priority and we can ignore the error. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Michał Winiarski <michal.winiarski@intel.com>
According to CI results this tests are either pass or skip, no failed assertions. Closing, thank you.
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.