igt@xe_drm_fdinfo@utilization-all-full-load - fail - CRITICAL: Test assertion failure function check_results CRITICAL: Failed assertion: percent < 105.0 CRITICAL: error: 249.908949 >= 105.000000

log on intel-gfx-ci.01.org

(xe_drm_fdinfo:1968) CRITICAL: Test assertion failure function check_results, file ../tests/intel/xe_drm_fdinfo.c:528:
(xe_drm_fdinfo:1968) CRITICAL: Failed assertion: percent < 105.0
(xe_drm_fdinfo:1968) CRITICAL: error: 249.908949 >= 105.000000
Subtest utilization-all-full-load failed.
**** DEBUG ****
(xe_drm_fdinfo:1968) DEBUG: rcs: spinner started
(xe_drm_fdinfo:1968) DEBUG: bcs: spinner started
(xe_drm_fdinfo:1968) DEBUG: ccs: spinner started
(xe_drm_fdinfo:1968) DEBUG: vcs: spinner started
(xe_drm_fdinfo:1968) DEBUG: vecs: spinner started
(xe_drm_fdinfo:1968) DEBUG: rcs: spinner ended (timestamp=12307011)
(xe_drm_fdinfo:1968) DEBUG: bcs: spinner ended (timestamp=4916006)
(xe_drm_fdinfo:1968) DEBUG: vcs: spinner ended (timestamp=4887259)
(xe_drm_fdinfo:1968) DEBUG: vecs: spinner ended (timestamp=4894278)
(xe_drm_fdinfo:1968) DEBUG: ccs: spinner ended (timestamp=4948631)
(xe_drm_fdinfo:1968) DEBUG: rcs: sample 1: cycles 0, total_cycles 1438737677
(xe_drm_fdinfo:1968) DEBUG: rcs: sample 2: cycles 12307346, total_cycles 1443662408
(xe_drm_fdinfo:1968) DEBUG: rcs: percent: 249.908949
(xe_drm_fdinfo:1968) CRITICAL: Test assertion failure function check_results, file ../tests/intel/xe_drm_fdinfo.c:528:```

added feature: GEM platform: LNL labels

The CI Bug Log issue associated to this bug has been updated by mczaplin.

New filters associated

• LNL: igt@xe_drm_fdinfo@utilization-all-full-load - fail - CRITICAL: Test assertion failure function check_results CRITICAL: Failed assertion: percent < 105.0 CRITICAL: error: 249.908949 >= 105.000000
  • https://intel-gfx-ci.01.org/tree/intel-xe/xe-2127-7cadd167321b3267a9803aba88f115fc9809d4ea/shard-lnl-8/igt@xe_drm_fdinfo@utilization-all-full-load.html

closed

This appears to be a duplicate of #2667 (closed) . Closing.

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.

mentioned in issue #3512 (closed)