Bug 105400

Summary: [CI] igt@pm_sseu@full-enable - fail - Test assertion failure function dbg_get_int, file pm_sseu.c - Failed assertion: pos != NULL
Product: DRI Reporter: Marta Löfstedt <marta.lofstedt>
Component: DRM/IntelAssignee: Marta Löfstedt <marta.lofstedt>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: BXT, GLK, KBL i915 features: power/Other

Description Marta Löfstedt 2018-03-08 14:55:12 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3894/shard-apl6/igt@pm_sseu@full-enable.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3894/shard-glkb2/igt@pm_sseu@full-enable.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3894/shard-kbl7/igt@pm_sseu@full-enable.html

(pm_sseu:1514) CRITICAL: Test assertion failure function dbg_get_int, file pm_sseu.c:113:
(pm_sseu:1514) CRITICAL: Failed assertion: pos != NULL
Subtest full-enable failed.
Comment 1 Marta Löfstedt 2018-03-08 14:57:29 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3894/commits.log

hint that sseu functionality has changed.
Comment 2 Lionel Landwerlin 2018-03-08 14:59:51 UTC
Should be fixed in :

commit 289202e876688338f439ded7613804ee67034e91 
Author: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Date:   Mon Feb 26 12:54:31 2018 +0000

    tests/pm_sseu: adapt debugfs parsing for newer kernels
Comment 3 Marta Löfstedt 2018-03-09 06:50:18 UTC
From IRC:
<marta_> tsa, is there something wrong with the IGT loop? last IGT run was IGT_4329 git@b4689dce ~ 2018-03-06 18:27:05, there are more commits on the git that are still not tested. Also, this means that we have had the same IGT and hence the same test ordering from CI_DRM_3880 to the current CI_DRM_3902

I.e. I can't close this yet since above commit hasn't been tested yet.
Comment 4 Marta Löfstedt 2018-03-09 11:20:32 UTC
(In reply to Marta Löfstedt from comment #3)
> From IRC:
> <marta_> tsa, is there something wrong with the IGT loop? last IGT run was
> IGT_4329 git@b4689dce ~ 2018-03-06 18:27:05, there are more commits on the
> git that are still not tested. Also, this means that we have had the same
> IGT and hence the same test ordering from CI_DRM_3880 to the current
> CI_DRM_3902
> 
> I.e. I can't close this yet since above commit hasn't been tested yet.

Reason was that IGT had build failures, this should now have been taken care off.

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.