intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for drm/i915/psr: Add missing check for I915_PSR_DEBUG_IRQ bit
Date: Sat, 11 Aug 2018 02:03:26 -0000	[thread overview]
Message-ID: <20180811020326.8593.3221@emeril.freedesktop.org> (raw)
In-Reply-To: <20180811005031.8888-1-dhinakaran.pandiyan@intel.com>

== Series Details ==

Series: drm/i915/psr: Add missing check for I915_PSR_DEBUG_IRQ bit
URL   : https://patchwork.freedesktop.org/series/48048/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4645_full -> Patchwork_9923_full =

== Summary - WARNING ==

  Minor unknown changes coming with Patchwork_9923_full need to be verified
  manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_9923_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_9923_full:

  === IGT changes ===

    ==== Warnings ====

    igt@kms_chv_cursor_fail@pipe-a-128x128-top-edge:
      shard-snb:          PASS -> SKIP

    
== Known issues ==

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

  === IGT changes ===

    ==== Issues hit ====

    igt@drv_suspend@fence-restore-untiled:
      shard-glk:          PASS -> FAIL (fdo#103375)

    igt@kms_cursor_legacy@all-pipes-torture-move:
      shard-snb:          PASS -> DMESG-WARN (fdo#107122)

    
  fdo#103375 https://bugs.freedesktop.org/show_bug.cgi?id=103375
  fdo#107122 https://bugs.freedesktop.org/show_bug.cgi?id=107122


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

    * Linux: CI_DRM_4645 -> Patchwork_9923

  CI_DRM_4645: 37a3cb069a7116ab9b04d3020c54557633dd180b @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4592: fce9638b2e60afce872b3056c19a729b1b3708be @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9923: 6a0549d5bcab0290e4ff6c2c22b63f9bbcedc147 @ git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit

== Logs ==

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

  parent reply	other threads:[~2018-08-11  2:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-11  0:50 [PATCH] drm/i915/psr: Add missing check for I915_PSR_DEBUG_IRQ bit Dhinakaran Pandiyan
2018-08-11  1:13 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-08-11  2:03 ` Patchwork [this message]
2018-08-12  8:00 ` [PATCH] " kbuild test robot
2018-08-12  9:26 ` kbuild test robot
2018-08-13 13:47 ` Maarten Lankhorst
2018-08-13 16:47   ` Rodrigo Vivi
2018-08-13 18:15     ` Pandiyan, Dhinakaran
2018-08-14  9:26       ` Maarten Lankhorst
2018-08-15 21:06         ` Rodrigo Vivi

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=20180811020326.8593.3221@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=dhinakaran.pandiyan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).