| Summary: | [CI] igt@gem_ctx_switch@basic-all-heavy - timeout - Test run time exceeded timeout value (300 seconds) | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Martin Peres <martin.peres> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | GLK, SNB | i915 features: | GEM/Other |
|
Description
Martin Peres
2018-03-16 17:57:52 UTC
This likely comes after Tomi changed the timeout from 600 to 300 seconds in piglit's igt.py. *** This bug has been marked as a duplicate of bug 105556 *** 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. I will archive this from cibuglog since the issue doesn't appear to happend again. I will not close since it was created by Martin. 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> Closing this now. |
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.