public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915: CTS fixes (rev3)
Date: Tue, 25 Jun 2019 12:57:04 -0000	[thread overview]
Message-ID: <20190625125704.20399.97467@emeril.freedesktop.org> (raw)
In-Reply-To: <20190625105832.19064-1-lionel.g.landwerlin@intel.com>

== Series Details ==

Series: drm/i915: CTS fixes (rev3)
URL   : https://patchwork.freedesktop.org/series/62437/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_6342 -> Patchwork_13413
====================================================

Summary
-------

  **FAILURE**

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

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

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

### IGT changes ###

#### Possible regressions ####

  * igt@i915_selftest@live_workarounds:
    - fi-cfl-guc:         [PASS][1] -> [DMESG-FAIL][2]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-cfl-guc/igt@i915_selftest@live_workarounds.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-cfl-guc/igt@i915_selftest@live_workarounds.html
    - fi-cml-u:           [PASS][3] -> [DMESG-FAIL][4]
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-cml-u/igt@i915_selftest@live_workarounds.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-cml-u/igt@i915_selftest@live_workarounds.html
    - fi-cfl-8109u:       [PASS][5] -> [DMESG-FAIL][6]
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-cfl-8109u/igt@i915_selftest@live_workarounds.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-cfl-8109u/igt@i915_selftest@live_workarounds.html
    - fi-whl-u:           [PASS][7] -> [DMESG-FAIL][8]
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-whl-u/igt@i915_selftest@live_workarounds.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-whl-u/igt@i915_selftest@live_workarounds.html
    - fi-icl-dsi:         [PASS][9] -> [DMESG-FAIL][10]
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-icl-dsi/igt@i915_selftest@live_workarounds.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-icl-dsi/igt@i915_selftest@live_workarounds.html
    - fi-icl-u3:          [PASS][11] -> [DMESG-FAIL][12]
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-icl-u3/igt@i915_selftest@live_workarounds.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-icl-u3/igt@i915_selftest@live_workarounds.html
    - fi-cfl-8700k:       [PASS][13] -> [DMESG-FAIL][14]
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-cfl-8700k/igt@i915_selftest@live_workarounds.html
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-cfl-8700k/igt@i915_selftest@live_workarounds.html
    - fi-icl-u2:          [PASS][15] -> [DMESG-FAIL][16]
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-icl-u2/igt@i915_selftest@live_workarounds.html
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-icl-u2/igt@i915_selftest@live_workarounds.html
    - fi-cml-u2:          [PASS][17] -> [DMESG-FAIL][18]
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-cml-u2/igt@i915_selftest@live_workarounds.html
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-cml-u2/igt@i915_selftest@live_workarounds.html

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

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

### IGT changes ###

#### Issues hit ####

  * igt@gem_exec_suspend@basic-s4-devices:
    - fi-icl-u3:          [PASS][19] -> [DMESG-WARN][20] ([fdo#107724])
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-icl-u3/igt@gem_exec_suspend@basic-s4-devices.html
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-icl-u3/igt@gem_exec_suspend@basic-s4-devices.html

  * igt@i915_pm_rpm@module-reload:
    - fi-skl-6770hq:      [PASS][21] -> [FAIL][22] ([fdo#108511])
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html

  * igt@kms_chamelium@dp-crc-fast:
    - fi-cml-u2:          [PASS][23] -> [FAIL][24] ([fdo#110627])
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html

  * igt@kms_frontbuffer_tracking@basic:
    - fi-icl-u2:          [PASS][25] -> [FAIL][26] ([fdo#103167])
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html

  
#### Possible fixes ####

  * igt@i915_selftest@live_blt:
    - fi-skl-iommu:       [INCOMPLETE][27] ([fdo#108602]) -> [PASS][28]
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-skl-iommu/igt@i915_selftest@live_blt.html
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-skl-iommu/igt@i915_selftest@live_blt.html

  * igt@i915_selftest@live_sanitycheck:
    - fi-icl-u3:          [DMESG-WARN][29] ([fdo#107724]) -> [PASS][30] +1 similar issue
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6342/fi-icl-u3/igt@i915_selftest@live_sanitycheck.html
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13413/fi-icl-u3/igt@i915_selftest@live_sanitycheck.html

  
  [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
  [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
  [fdo#108511]: https://bugs.freedesktop.org/show_bug.cgi?id=108511
  [fdo#108602]: https://bugs.freedesktop.org/show_bug.cgi?id=108602
  [fdo#110627]: https://bugs.freedesktop.org/show_bug.cgi?id=110627


Participating hosts (53 -> 45)
------------------------------

  Missing    (8): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-bwr-2160 fi-icl-y fi-byt-clapper fi-bdw-samus 


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

  * Linux: CI_DRM_6342 -> Patchwork_13413

  CI_DRM_6342: 6eef272b254b34200129af8f2ec1e4cfe1ca6bff @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_5067: 5eafa33dbdb1d3c190ac5060161c45152e9a298e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_13413: 5e4d6c80907ce04521f6a3ea58b7eca2dd8193bc @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

5e4d6c80907c drm/i915/icl: whitelist PS_(DEPTH|INVOCATION)_COUNT
73c970b28af1 drm/i915: whitelist PS_(DEPTH|INVOCATION)_COUNT

== Logs ==

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

  parent reply	other threads:[~2019-06-25 12:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 10:58 [PATCH v3 0/2] drm/i915: CTS fixes Lionel Landwerlin
2019-06-25 10:58 ` [PATCH v3 1/2] drm/i915: whitelist PS_(DEPTH|INVOCATION)_COUNT Lionel Landwerlin
2019-06-25 10:58 ` [PATCH v3 2/2] drm/i915/icl: " Lionel Landwerlin
2019-06-25 12:15 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTS fixes (rev3) Patchwork
2019-06-25 12:57 ` Patchwork [this message]
2019-06-25 13:09   ` ✗ Fi.CI.BAT: failure " Lionel Landwerlin
2019-06-25 13:14     ` Chris Wilson
2019-06-25 13:24       ` Lionel Landwerlin
2019-06-25 13:28         ` Chris Wilson
2019-06-25 13:16     ` Chris Wilson
2019-06-25 13:19       ` Lionel Landwerlin

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