Summary: | [CI][DRMTIP] igt@drv_suspend@shrink - dmesg-warn - Out of memory: Kill process 2520 (drv_suspend) score 1865 or sacrifice child | ||
---|---|---|---|
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: | BXT, CFL, ICL, SKL | i915 features: |
Description
Martin Peres
2018-09-10 10:48:41 UTC
The test creatively misuses oom to see what happens if we encounter one while trying to suspend. Despite Java's best efforts to screw up (WHAT IS IT DOING WHILE THE TEST IS RUNNING! AGAIN!!!) it did not. This should not have been marked as DMESG-WARN. (In reply to Chris Wilson from comment #1) > This should not have been marked as DMESG-WARN. So, this is a bug then ;) Also seen on APL: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4695/shard-apl7/igt@drv_suspend@shrink.html Also seen on ICL: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_134/fi-icl-u/igt@drv_suspend@shrink.html A CI Bug Log filter associated to this bug has been updated: {- APL CFL ICL: igt@drv_suspend@shrink - dmesg-warn - Out of memory: Kill process \d+ (drv_suspend) score \d+ or sacrifice child -} {+ SKL APL CFL ICL: igt@drv_suspend@shrink - dmesg-warn - Out of memory: Kill process \d+ (drv_suspend) score \d+ or sacrifice child +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_169/fi-skl-gvtdvm/igt@i915_suspend@shrink.html A CI Bug Log filter associated to this bug has been updated: {- SKL APL CFL ICL: igt@drv_suspend@shrink - dmesg-warn - Out of memory: Kill process \d+ (drv_suspend) score \d+ or sacrifice child -} {+ SKL APL CFL ICL: igt@drv_suspend@shrink - dmesg-warn - Out of memory: Kill process \d+ (i915_suspend) score \d+ or sacrifice child +} No new failures caught with the new filter The test got removed. Problem solved :D The CI Bug Log issue associated to this bug has been archived. New failures matching the above filters will not be associated to this bug anymore. |
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.