Bug 108073 - [CI][SHARDS] igt@gem_cpu_reloc@full - incomplete
Summary: [CI][SHARDS] igt@gem_cpu_reloc@full - incomplete
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: IGT (show other bugs)
Version: DRI git
Hardware: Other All
: highest blocker
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard: ReadyForDev
Keywords:
: 108074 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-09-26 10:05 UTC by Martin Peres
Modified: 2019-02-19 08:21 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: GEM/Other


Attachments

Description Martin Peres 2018-09-26 10:05:25 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_117/fi-skl-caroline/igt@gem_cpu_reloc@full.html

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4876/shard-skl1/igt@gem_cpu_reloc@full.html

	
<6> [109.855608] Console: switching to colour dummy device 80x25
<6> [109.855981] [IGT] gem_cpu_reloc: executing
<6> [109.918826] [IGT] gem_cpu_reloc: starting subtest full
<6> [109.984077] gem_cpu_reloc (901): drop_caches: 4
<7> [111.748837] [drm:intel_power_well_enable [i915]] enabling DC off
<7> [111.749509] [drm:gen9_set_dc_state [i915]] Setting DC state from 02 to 00
<7> [471.906089] [drm:intel_power_well_disable [i915]] disabling DC off
<7> [471.906416] [drm:gen9_dc_off_power_well_disable [i915]] Enabling DC6
<7> [471.906583] [drm:gen9_set_dc_state [i915]] Setting DC state from 00 to 02
<6> [471.946800] Console: switching to colour frame buffer device 300x100
Comment 1 Chris Wilson 2018-11-21 20:52:21 UTC
CI bug, declares a timeout and aborts.
Comment 2 Chris Wilson 2018-11-26 20:54:19 UTC
Looking further, it's quite a serious bug.

<7>[  268.714297] [IGT] gem_cpu_reloc: executing
<7>[  268.789099] [IGT] gem_cpu_reloc: starting subtest full

yet

[30/79] ( 882s left) gem_cpu_reloc (full)
Child refuses to die. Aborting.
Warning: Cannot open result directory 30
Starting subtest: full
Timeout. Killing the current test with SIGTERM.
Timeout. Killing the current test with SIGKILL.
Closing watchdogs
Closing watchdogs
Done.

So it tried to kill the child before any timeout, even before it began executing the subtest, i.e <70ms. And closed the watchdogs twice.

Fork() gone astray?
Comment 3 Chris Wilson 2018-11-27 09:41:33 UTC
commit a6b514d242bddd9457f04bb25cde0ddf85032b65 (upstream/master, origin/master, origin/HEAD)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Nov 26 21:35:40 2018 +0000

    runner: Be patient for processes to die
    
    Some machines are very slow and some processes hog a lot of resources
    and so take much longer than a mere 2s to be terminated. Be patient.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108073
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Reviewed-by: Petri Latvala <petri.latvala@intel.com>


Assuming this did cure it.
Comment 4 Chris Wilson 2018-11-27 09:43:43 UTC
*** Bug 108074 has been marked as a duplicate of this bug. ***
Comment 5 Lakshmi 2019-02-19 08:21:28 UTC
Last seen CI_DRM_5296_full (2 months, 1 week / 1138 runs ago).
This bug has been archived. Closing this bug.


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.