Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Lyude Paul <lyude@redhat.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/atomic_helper: Stop modesets on unregistered connectors harder
Date: Tue, 16 Oct 2018 03:14:15 -0000	[thread overview]
Message-ID: <20181016031415.318.99159@emeril.freedesktop.org> (raw)
In-Reply-To: <20181016023306.27417-1-lyude@redhat.com>

== Series Details ==

Series: drm/atomic_helper: Stop modesets on unregistered connectors harder
URL   : https://patchwork.freedesktop.org/series/51041/
State : failure

== Summary ==

= CI Bug Log - changes from CI_DRM_4984 -> Patchwork_10466 =

== Summary - FAILURE ==

  Serious unknown changes coming with Patchwork_10466 absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_10466, please notify your bug team to allow them
  to document this new failure mode, which will reduce false positives in CI.

  External URL: https://patchwork.freedesktop.org/api/1.0/series/51041/revisions/1/mbox/

== Possible new issues ==

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

  === IGT changes ===

    ==== Possible regressions ====

    igt@drv_module_reload@basic-reload:
      fi-kbl-8809g:       PASS -> DMESG-WARN +3

    igt@drv_module_reload@basic-reload-inject:
      fi-skl-6260u:       PASS -> DMESG-WARN
      fi-snb-2600:        PASS -> DMESG-WARN
      fi-kbl-7560u:       PASS -> DMESG-WARN
      fi-kbl-guc:         PASS -> DMESG-WARN
      fi-skl-6770hq:      PASS -> DMESG-WARN
      fi-bwr-2160:        PASS -> DMESG-WARN
      fi-kbl-r:           PASS -> DMESG-WARN
      fi-cfl-s3:          PASS -> DMESG-WARN
      fi-byt-clapper:     PASS -> DMESG-WARN
      fi-gdg-551:         PASS -> DMESG-WARN
      fi-icl-u2:          PASS -> DMESG-WARN
      fi-bsw-kefka:       PASS -> DMESG-WARN
      fi-bdw-gvtdvm:      PASS -> DMESG-WARN
      fi-ilk-650:         PASS -> DMESG-WARN
      fi-bsw-n3050:       PASS -> DMESG-WARN
      fi-cnl-u:           PASS -> DMESG-WARN
      fi-kbl-7567u:       PASS -> DMESG-WARN +2
      fi-glk-j4005:       PASS -> DMESG-WARN
      fi-skl-iommu:       PASS -> DMESG-WARN
      fi-ivb-3770:        PASS -> DMESG-WARN
      fi-skl-gvtdvm:      PASS -> DMESG-WARN
      fi-whl-u:           PASS -> DMESG-WARN
      fi-skl-6700hq:      PASS -> DMESG-WARN
      fi-ivb-3520m:       PASS -> DMESG-WARN
      fi-glk-dsi:         PASS -> DMESG-WARN
      fi-bdw-5557u:       PASS -> DMESG-WARN
      {fi-apl-guc}:       PASS -> DMESG-WARN
      fi-cfl-8700k:       PASS -> DMESG-WARN
      fi-icl-u:           NOTRUN -> DMESG-WARN
      fi-kbl-x1275:       PASS -> DMESG-WARN
      fi-skl-6600u:       PASS -> DMESG-WARN
      fi-pnv-d510:        PASS -> DMESG-WARN
      fi-skl-guc:         PASS -> DMESG-WARN
      fi-cfl-guc:         PASS -> DMESG-WARN
      fi-skl-6700k2:      PASS -> DMESG-WARN
      fi-elk-e7500:       PASS -> DMESG-WARN

    igt@pm_rpm@module-reload:
      fi-cfl-8109u:       PASS -> DMESG-WARN +2
      fi-kbl-7500u:       PASS -> DMESG-WARN +2

    
== Known issues ==

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

  === IGT changes ===

    ==== Issues hit ====

    igt@drv_getparams_basic@basic-subslice-total:
      fi-snb-2520m:       PASS -> DMESG-WARN (fdo#103713) +10

    igt@drv_module_reload@basic-reload-inject:
      fi-bxt-j4205:       PASS -> DMESG-WARN (fdo#107821)
      fi-bxt-dsi:         PASS -> DMESG-WARN (fdo#107821)
      fi-hsw-4770:        PASS -> DMESG-WARN (fdo#107924)
      fi-hsw-peppy:       PASS -> DMESG-WARN (fdo#107924)
      fi-hsw-4770r:       PASS -> DMESG-WARN (fdo#107924)

    igt@drv_selftest@live_hangcheck:
      fi-icl-u:           NOTRUN -> INCOMPLETE (fdo#108315)

    igt@kms_flip@basic-flip-vs-modeset:
      fi-hsw-4770r:       PASS -> DMESG-WARN (fdo#105602) +1

    
    ==== Possible fixes ====

    igt@kms_frontbuffer_tracking@basic:
      fi-byt-clapper:     FAIL (fdo#103167) -> PASS

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

  fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
  fdo#103713 https://bugs.freedesktop.org/show_bug.cgi?id=103713
  fdo#105602 https://bugs.freedesktop.org/show_bug.cgi?id=105602
  fdo#107821 https://bugs.freedesktop.org/show_bug.cgi?id=107821
  fdo#107924 https://bugs.freedesktop.org/show_bug.cgi?id=107924
  fdo#108315 https://bugs.freedesktop.org/show_bug.cgi?id=108315


== Participating hosts (53 -> 47) ==

  Additional (1): fi-icl-u 
  Missing    (7): fi-ilk-m540 fi-hsw-4200u fi-byt-j1900 fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-n2820 


== Build changes ==

    * Linux: CI_DRM_4984 -> Patchwork_10466

  CI_DRM_4984: 90b59df999a13a6405f8d7ece08a69120a9b361a @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4678: 9310a1265ceabeec736bdf0a76e1e0357c76c0b1 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_10466: 26909bc1ea409e674f04fca95b55bed4c69caa9c @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

26909bc1ea40 drm/atomic_helper: Stop modesets on unregistered connectors harder

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10466/issues.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-10-16  3:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16  2:33 [PATCH] drm/atomic_helper: Stop modesets on unregistered connectors harder Lyude Paul
2018-10-16  3:14 ` Patchwork [this message]
2018-10-16 12:48 ` Daniel Vetter

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=20181016031415.318.99159@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lyude@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox