All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915: Remove whitelist application from ringbuffer backend
Date: Thu, 29 Nov 2018 14:27:36 -0000	[thread overview]
Message-ID: <20181129142736.5828.34996@emeril.freedesktop.org> (raw)
In-Reply-To: <20181129134128.7994-1-tvrtko.ursulin@linux.intel.com>

== Series Details ==

Series: drm/i915: Remove whitelist application from ringbuffer backend
URL   : https://patchwork.freedesktop.org/series/53243/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_5222 -> Patchwork_10954
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with Patchwork_10954 absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_10954, 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/53243/revisions/1/mbox/

Possible new issues
-------------------

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

### IGT changes ###

#### Possible regressions ####

  * igt@i915_selftest@live_sanitycheck:
    - fi-bxt-dsi:         PASS -> DMESG-WARN

  * {igt@runner@aborted}:
    - fi-bxt-dsi:         NOTRUN -> FAIL

  
Known issues
------------

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

### IGT changes ###

#### Issues hit ####

  * igt@kms_frontbuffer_tracking@basic:
    - {fi-icl-u3}:        PASS -> FAIL [fdo#103167]

  * {igt@runner@aborted}:
    - {fi-icl-y}:         NOTRUN -> FAIL [fdo#108070]

  
#### Possible fixes ####

  * igt@gem_mmap_gtt@basic:
    - fi-glk-dsi:         INCOMPLETE [fdo#103359] / [k.org#198133] -> 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#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359
  [fdo#108070]: https://bugs.freedesktop.org/show_bug.cgi?id=108070
  [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133


Participating hosts (49 -> 44)
------------------------------

  Additional (1): fi-icl-y 
  Missing    (6): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 


Build changes
-------------

    * Linux: CI_DRM_5222 -> Patchwork_10954

  CI_DRM_5222: a6f85043a0ca86eb0072e69bf92b77f7d9d6d5d5 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4735: b05c028ccdb6ac8e8d8499a041bb14dfe358ee26 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_10954: 39a3d63b054d5073c2cecb6d27757ae3d7095ddc @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

39a3d63b054d drm/i915: Remove whitelist application from ringbuffer backend

== Logs ==

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

  parent reply	other threads:[~2018-11-29 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29 13:41 [PATCH] drm/i915: Remove whitelist application from ringbuffer backend Tvrtko Ursulin
2018-11-29 13:46 ` Chris Wilson
2018-11-29 14:27 ` Patchwork [this message]
2018-11-29 14:47   ` ✗ Fi.CI.BAT: failure for " Tvrtko Ursulin
2018-11-29 16:48 ` ✗ Fi.CI.BAT: failure for drm/i915: Remove whitelist application from ringbuffer backend (rev2) Patchwork
2018-11-29 17:48 ` ✓ Fi.CI.BAT: success for drm/i915: Remove whitelist application from ringbuffer backend (rev3) Patchwork
2018-11-30 15:11   ` Tvrtko Ursulin
2018-11-30  8:21 ` ✓ Fi.CI.IGT: " Patchwork

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=20181129142736.5828.34996@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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.