All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Srivatsa, Anusha" <anusha.srivatsa@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.BAT: failure for drm/i915/dmc: Load DMC on DG2
Date: Thu, 14 Apr 2022 02:21:53 +0000	[thread overview]
Message-ID: <1dc16784b340495f894a3fb352ad8570@intel.com> (raw)
In-Reply-To: <164988007061.28395.18042961133974426704@emeril.freedesktop.org>

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



From: Patchwork <patchwork@emeril.freedesktop.org>
Sent: Wednesday, April 13, 2022 1:01 PM
To: Srivatsa, Anusha <anusha.srivatsa@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915/dmc: Load DMC on DG2

Patch Details
Series:

drm/i915/dmc: Load DMC on DG2

URL:

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

State:

failure

Details:

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

CI Bug Log - changes from CI_DRM_11496 -> Patchwork_102630v1
Summary

FAILURE

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

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

External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v1/index.html

Participating hosts (50 -> 46)

Additional (1): fi-pnv-d510
Missing (5): fi-cml-u2 fi-bsw-cyan fi-icl-u2 bat-hsw-1 fi-bdw-samus

Possible new issues

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

IGT changes
Possible regressions

  *   igt@i915_selftest@live@hangcheck:

     *   fi-hsw-4770: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11496/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v1/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html>

The failure reported is not because of the changes introduced.
Anusha
Known issues

Here are the changes found in Patchwork_102630v1 that come from known issues:

IGT changes
Issues hit

  *   igt@kms_busy@basic@modeset:

     *   fi-tgl-u2: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11496/fi-tgl-u2/igt@kms_busy@basic@modeset.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v1/fi-tgl-u2/igt@kms_busy@basic@modeset.html> (i915#402<https://gitlab.freedesktop.org/drm/intel/issues/402>)

  *   igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c:

     *   fi-pnv-d510: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v1/fi-pnv-d510/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#5341<https://gitlab.freedesktop.org/drm/intel/issues/5341>)

  *   igt@prime_vgem@basic-userptr:

     *   fi-pnv-d510: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v1/fi-pnv-d510/igt@prime_vgem@basic-userptr.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +39 similar issues

  *   igt@runner@aborted:

     *   fi-bdw-5557u: NOTRUN -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v1/fi-bdw-5557u/igt@runner@aborted.html> (i915#4312<https://gitlab.freedesktop.org/drm/intel/issues/4312>)

Possible fixes

  *   igt@gem_exec_suspend@basic-s3@smem:

     *   fi-bdw-5557u: INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11496/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html> (i915#146<https://gitlab.freedesktop.org/drm/intel/issues/146>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v1/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html>

  *   igt@i915_pm_rps@basic-api:

     *   {bat-dg2-9}: FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11496/bat-dg2-9/igt@i915_pm_rps@basic-api.html> -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v1/bat-dg2-9/igt@i915_pm_rps@basic-api.html>

  *   igt@i915_selftest@live@gt_heartbeat:

     *   fi-skl-guc: DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11496/fi-skl-guc/igt@i915_selftest@live@gt_heartbeat.html> -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v1/fi-skl-guc/igt@i915_selftest@live@gt_heartbeat.html>

  *   igt@i915_selftest@live@hangcheck:

     *   fi-snb-2600: INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11496/fi-snb-2600/igt@i915_selftest@live@hangcheck.html> (i915#3921<https://gitlab.freedesktop.org/drm/intel/issues/3921>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v1/fi-snb-2600/igt@i915_selftest@live@hangcheck.html>

  *   igt@kms_busy@basic@flip:

     *   {bat-adlp-6}: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11496/bat-adlp-6/igt@kms_busy@basic@flip.html> (i915#3576<https://gitlab.freedesktop.org/drm/intel/issues/3576>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102630v1/bat-adlp-6/igt@kms_busy@basic@flip.html>

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

Build changes

  *   Linux: CI_DRM_11496 -> Patchwork_102630v1

CI-20190529: 20190529
CI_DRM_11496: 6dec7597a5027afe15cf36f1e796a0f2e5189741 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6420: a3885810ccc0ce9e6552a20c910a0a322eca466c @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_102630v1: 6dec7597a5027afe15cf36f1e796a0f2e5189741 @ git://anongit.freedesktop.org/gfx-ci/linux

== Linux commits ==

d2f87101f94b drm/i915/dmc: Load DMC on DG2

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

  reply	other threads:[~2022-04-14  2:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  0:57 [Intel-gfx] [PATCH] drm/i915/dmc: Load DMC on DG2 Anusha Srivatsa
2022-04-13 20:01 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-04-14  2:21   ` Srivatsa, Anusha [this message]
2022-04-13 20:56 ` [Intel-gfx] [PATCH] " Rodrigo Vivi
2022-04-14  3:05 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dmc: Load DMC on DG2 (rev3) Patchwork
2022-04-14 18:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4) Patchwork
2022-04-14 20:54   ` Srivatsa, Anusha
2022-04-15  4:37     ` Lucas De Marchi
2022-04-15  6:39       ` Lucas De Marchi
2022-04-16 16:27       ` Sarvela, Tomi P
2022-04-14 21:44 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-15  4:32 ` [Intel-gfx] [PATCH] drm/i915/dmc: Load DMC on DG2 Lucas De Marchi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1dc16784b340495f894a3fb352ad8570@intel.com \
    --to=anusha.srivatsa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.