All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Navare, Manasi D" <manasi.d.navare@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: "Syrjala, Ville" <ville.syrjala@intel.com>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.BAT: failure for series starting with [v3,1/6] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes
Date: Wed, 28 Oct 2020 23:44:19 +0000	[thread overview]
Message-ID: <882ed7adf96146a192df28858d23ecaa@intel.com> (raw)
In-Reply-To: <160392787406.21341.9020044955134417038@emeril.freedesktop.org>


[-- Attachment #1.1: Type: text/plain, Size: 10971 bytes --]

I don’t see how these failures are related to the patch series

Manasi

From: Patchwork <patchwork@emeril.freedesktop.org>
Sent: Wednesday, October 28, 2020 4:31 PM
To: Navare, Manasi D <manasi.d.navare@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [v3,1/6] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes

Patch Details
Series:

series starting with [v3,1/6] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes

URL:

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

State:

failure

Details:

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

CI Bug Log - changes from CI_DRM_9214 -> Patchwork_18802
Summary

FAILURE

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

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_18802, 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_18802/index.html

Possible new issues

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

IGT changes
Possible regressions

  *   igt@kms_force_connector_basic@force-load-detect:
     *   fi-hsw-4770: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-hsw-4770/igt@kms_force_connector_basic@force-load-detect.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-hsw-4770/igt@kms_force_connector_basic@force-load-detect.html>
     *   fi-elk-e7500: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-elk-e7500/igt@kms_force_connector_basic@force-load-detect.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-elk-e7500/igt@kms_force_connector_basic@force-load-detect.html>
     *   fi-ivb-3770: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-ivb-3770/igt@kms_force_connector_basic@force-load-detect.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-ivb-3770/igt@kms_force_connector_basic@force-load-detect.html>
     *   fi-byt-j1900: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-byt-j1900/igt@kms_force_connector_basic@force-load-detect.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-byt-j1900/igt@kms_force_connector_basic@force-load-detect.html>
     *   fi-blb-e6850: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-blb-e6850/igt@kms_force_connector_basic@force-load-detect.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-blb-e6850/igt@kms_force_connector_basic@force-load-detect.html>
     *   fi-ilk-650: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-ilk-650/igt@kms_force_connector_basic@force-load-detect.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-ilk-650/igt@kms_force_connector_basic@force-load-detect.html>
     *   fi-snb-2520m: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-snb-2520m/igt@kms_force_connector_basic@force-load-detect.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-snb-2520m/igt@kms_force_connector_basic@force-load-detect.html>
     *   fi-bwr-2160: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-bwr-2160/igt@kms_force_connector_basic@force-load-detect.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-bwr-2160/igt@kms_force_connector_basic@force-load-detect.html>
     *   fi-snb-2600: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-snb-2600/igt@kms_force_connector_basic@force-load-detect.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-snb-2600/igt@kms_force_connector_basic@force-load-detect.html>
  *   igt@runner@aborted:
     *   fi-pnv-d510: NOTRUN -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-pnv-d510/igt@runner@aborted.html>
     *   fi-gdg-551: NOTRUN -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-gdg-551/igt@runner@aborted.html>
     *   fi-bwr-2160: NOTRUN -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-bwr-2160/igt@runner@aborted.html>
     *   fi-blb-e6850: NOTRUN -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-blb-e6850/igt@runner@aborted.html>

New tests

New tests have been introduced between CI_DRM_9214 and Patchwork_18802:

New CI tests (1)

  *   boot:
     *   Statuses : 39 pass(s)
     *   Exec time: [0.0] s

Known issues

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

IGT changes
Issues hit

  *   igt@i915_module_load@reload:
     *   fi-tgl-u2: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-tgl-u2/igt@i915_module_load@reload.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-tgl-u2/igt@i915_module_load@reload.html> (i915#1982<https://gitlab.freedesktop.org/drm/intel/issues/1982> / k.org#205379<https://bugzilla.kernel.org/show_bug.cgi?id=205379>)
  *   igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
     *   fi-bsw-kefka: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html> (i915#1982<https://gitlab.freedesktop.org/drm/intel/issues/1982>)
  *   igt@kms_flip@basic-flip-vs-dpms@c-edp1:
     *   fi-tgl-y: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-tgl-y/igt@kms_flip@basic-flip-vs-dpms@c-edp1.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-tgl-y/igt@kms_flip@basic-flip-vs-dpms@c-edp1.html> (i915#1982<https://gitlab.freedesktop.org/drm/intel/issues/1982>)
  *   igt@kms_force_connector_basic@force-load-detect:
     *   fi-pnv-d510: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-pnv-d510/igt@kms_force_connector_basic@force-load-detect.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-pnv-d510/igt@kms_force_connector_basic@force-load-detect.html> (i915#299<https://gitlab.freedesktop.org/drm/intel/issues/299>)
     *   fi-gdg-551: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-gdg-551/igt@kms_force_connector_basic@force-load-detect.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-gdg-551/igt@kms_force_connector_basic@force-load-detect.html> (i915#172<https://gitlab.freedesktop.org/drm/intel/issues/172>)
  *   igt@prime_self_import@basic-with_two_bos:
     *   fi-tgl-y: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-tgl-y/igt@prime_self_import@basic-with_two_bos.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-tgl-y/igt@prime_self_import@basic-with_two_bos.html> (i915#402<https://gitlab.freedesktop.org/drm/intel/issues/402>) +1 similar issue

Possible fixes

  *   igt@debugfs_test@read_all_entries:
     *   fi-tgl-y: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-tgl-y/igt@debugfs_test@read_all_entries.html> (i915#402<https://gitlab.freedesktop.org/drm/intel/issues/402>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-tgl-y/igt@debugfs_test@read_all_entries.html> +2 similar issues
     *   {fi-kbl-7560u}: INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-kbl-7560u/igt@debugfs_test@read_all_entries.html> (i915#2417<https://gitlab.freedesktop.org/drm/intel/issues/2417>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-kbl-7560u/igt@debugfs_test@read_all_entries.html>
  *   igt@i915_pm_rpm@basic-pci-d3-state:
     *   fi-apl-guc: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-apl-guc/igt@i915_pm_rpm@basic-pci-d3-state.html> (i915#1635<https://gitlab.freedesktop.org/drm/intel/issues/1635> / i915#1982<https://gitlab.freedesktop.org/drm/intel/issues/1982>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-apl-guc/igt@i915_pm_rpm@basic-pci-d3-state.html>
  *   igt@kms_busy@basic@flip:
     *   fi-kbl-soraka: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-kbl-soraka/igt@kms_busy@basic@flip.html> (i915#1982<https://gitlab.freedesktop.org/drm/intel/issues/1982>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-kbl-soraka/igt@kms_busy@basic@flip.html>
     *   fi-tgl-y: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-tgl-y/igt@kms_busy@basic@flip.html> (i915#1982<https://gitlab.freedesktop.org/drm/intel/issues/1982>) -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-tgl-y/igt@kms_busy@basic@flip.html>

Warnings

  *   igt@gem_exec_suspend@basic-s3:
     *   fi-tgl-y: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-tgl-y/igt@gem_exec_suspend@basic-s3.html> (i915#2411<https://gitlab.freedesktop.org/drm/intel/issues/2411>) -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-tgl-y/igt@gem_exec_suspend@basic-s3.html> (i915#2411<https://gitlab.freedesktop.org/drm/intel/issues/2411> / i915#402<https://gitlab.freedesktop.org/drm/intel/issues/402>)
  *   igt@i915_pm_rpm@module-reload:
     *   fi-tgl-y: DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9214/fi-tgl-y/igt@i915_pm_rpm@module-reload.html> (i915#2411<https://gitlab.freedesktop.org/drm/intel/issues/2411>) -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18802/fi-tgl-y/igt@i915_pm_rpm@module-reload.html> (i915#1982<https://gitlab.freedesktop.org/drm/intel/issues/1982> / i915#2411<https://gitlab.freedesktop.org/drm/intel/issues/2411>)

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

Participating hosts (41 -> 39)

Missing (2): fi-bsw-cyan fi-bdw-samus

Build changes

  *   Linux: CI_DRM_9214 -> Patchwork_18802

CI-20190529: 20190529
CI_DRM_9214: c485050a56cf0edaed15b8297d5540bd0f4310b9 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5827: 7fd7e3fb8b42eb4e62a4575f6edc5a048e5bec3d @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_18802: 1388a0c36ca0a250e8f8dc39240096d044d5cb65 @ git://anongit.freedesktop.org/gfx-ci/linux

== Linux commits ==

1388a0c36ca0 drm/i915/dp: Allow big joiner modes in intel_dp_mode_valid(), v3.
779bec036a45 drm/i915/dp: Prep for bigjoiner atomic check
a5f14d0b240f drm/i915: Pass intel_atomic_state instead of drm_atomic_state
f4900e21412a drm/i915: Add pipe_mode readout in verify_crtc_state
7b5090a4c566 drm/i915: Add hw.pipe_mode to allow bigjoiner pipe/transcoder split
29b307e050f4 drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes

[-- Attachment #1.2: Type: text/html, Size: 32872 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2020-10-28 23:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 21:42 [Intel-gfx] [PATCH v3 1/6] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes Manasi Navare
2020-10-28 21:42 ` [Intel-gfx] [PATCH v3 2/6] drm/i915: Add hw.pipe_mode to allow bigjoiner pipe/transcoder split Manasi Navare
2020-10-28 21:42 ` [Intel-gfx] [PATCH v3 3/6] drm/i915: Add pipe_mode readout in verify_crtc_state Manasi Navare
2020-10-28 21:42 ` [Intel-gfx] [PATCH v3 4/6] drm/i915: Pass intel_atomic_state instead of drm_atomic_state Manasi Navare
2020-10-28 21:42 ` [Intel-gfx] [PATCH v3 5/6] drm/i915/dp: Prep for bigjoiner atomic check Manasi Navare
2020-10-28 21:42 ` [Intel-gfx] [PATCH v3 6/6] drm/i915/dp: Allow big joiner modes in intel_dp_mode_valid(), v3 Manasi Navare
2020-10-28 23:00 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v3,1/6] drm/i915/dp: Some reshuffling in mode_valid as prep for bigjoiner modes Patchwork
2020-10-28 23:31 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-10-28 23:44   ` Navare, Manasi D [this message]

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=882ed7adf96146a192df28858d23ecaa@intel.com \
    --to=manasi.d.navare@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@intel.com \
    /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.