https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bsw-n3050/igt@gem_ctx_switch@basic-all-heavy.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-byt-j1900/igt@gem_ctx_switch@basic-all-heavy.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-byt-n2820/igt@gem_ctx_switch@basic-all-heavy.html From run.logs: running: igt/gem_ctx_switch/basic-all-heavy [09/97] skip: 6, pass: 3 / owatch: TIMEOUT!
*** Bug 105561 has been marked as a duplicate of this bug. ***
(In reply to Martin Peres from comment #1) > *** Bug 105561 has been marked as a duplicate of this bug. *** This is for sure not a duplicate of bug 105556, since that bug is softdog incomplete and this is piglit timeout due to change in the CI system configuration. Before the configuration change the softdog did not hit the pinpointed machines on the test.
commit 20b8799898c844ad57e9cdb0238ffb7a44140d89 (HEAD, upstream/master) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Mar 16 15:53:57 2018 +0000 igt/gem_ctx_switch: Measure qlen for timing loops Some platforms may execute the heavy workload very slowly, such that using a batch of 1024 takes tens of seconds and immediately overrunning the 5s timeout on a pass. Added up over a few dozen passes, this turns a 120 second test into 10 minutes. Counter this by doing a warmup loop to estimate the appropriate queue len for timing. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Will take some time to get results since this is only reproduced when BAT machines run the shards testlist.
Was not reproduced on drmtip_7
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.