Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Suspend / resume backup- and restore of LMEM. (rev9)

Vudum, Lakshminarayana
2021-09-23T02:11:50Z

[-- Attachment #1: Type: text/plain, Size: 2045 bytes --]

Failure is related to https://gitlab.freedesktop.org/drm/intel/-/issues/3797. I have re-reported the results after updating the CI bug log filters.

Lakshmi.

From: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Sent: Wednesday, September 22, 2021 11:07 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Suspend / resume backup- and restore of LMEM. (rev9)

On 9/22/21 11:05 AM, Patchwork wrote:
Patch Details
Series:

drm/i915: Suspend / resume backup- and restore of LMEM. (rev9)

URL:

https://patchwork.freedesktop.org/series/94278/

State:

failure

Details:

https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21124/index.html

CI Bug Log - changes from CI_DRM_10622_full -> Patchwork_21124_full
Summary

FAILURE

Serious unknown changes coming with Patchwork_21124_full absolutely need to be
verified manually.

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_21124_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.

Possible new issues

Here are the unknown changes that may have been introduced in Patchwork_21124_full:

IGT changes
Possible regressions

* igt@gem_exec_schedule@u-submit-golden-slice@rcs0:

* shard-tglb: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10622/shard-tglb3/igt@gem_exec_schedule@u-submit-golden-slice@rcs0.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21124/shard-tglb6/igt@gem_exec_schedule@u-submit-golden-slice@rcs0.html>

Lakshmi, this failure is unrelated.

The igt@gem_exec_schedule@u-submit-golden-slice plus some other subtests have been broken since igt commit

a9987a8d tests/i915/gem_exec_schedule: Convert to intel_ctx_t (v3)

Although the tests typically says SUCCESS, it's because they typically are interrupted by the watchdog and move on.

Thanks,

Thomas

[-- Attachment #2: Type: text/html, Size: 9977 bytes --]