Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for New DDB allocation algorithm
Date: Thu, 06 Dec 2018 17:44:59 -0000	[thread overview]
Message-ID: <20181206174459.2790.92570@emeril.freedesktop.org> (raw)
In-Reply-To: <20181206170944.16539-1-matthew.d.roper@intel.com>

== Series Details ==

Series: New DDB allocation algorithm
URL   : https://patchwork.freedesktop.org/series/53682/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_5277 -> Patchwork_11038
====================================================

Summary
-------

  **FAILURE**

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

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

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

### IGT changes ###

#### Possible regressions ####

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
    - fi-glk-j4005:       PASS -> DMESG-FAIL +1
    - fi-skl-iommu:       PASS -> DMESG-FAIL +1
    - fi-whl-u:           PASS -> DMESG-FAIL +1
    - fi-skl-6700hq:      PASS -> FAIL +2
    - fi-kbl-7560u:       PASS -> DMESG-FAIL +1
    - fi-cfl-8109u:       PASS -> DMESG-FAIL +1
    - fi-cfl-guc:         PASS -> DMESG-FAIL +1
    - fi-skl-6260u:       PASS -> DMESG-FAIL +1
    - fi-bxt-j4205:       PASS -> DMESG-FAIL +1
    - {fi-icl-u3}:        PASS -> DMESG-FAIL +1
    - fi-skl-6770hq:      PASS -> DMESG-FAIL

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
    - fi-kbl-x1275:       PASS -> DMESG-FAIL +1
    - fi-cfl-8700k:       PASS -> DMESG-FAIL +1
    - fi-apl-guc:         PASS -> DMESG-FAIL +1
    - fi-glk-dsi:         NOTRUN -> DMESG-FAIL +1
    - fi-skl-6700hq:      PASS -> DMESG-FAIL
    - fi-skl-gvtdvm:      PASS -> DMESG-FAIL +1
    - fi-bxt-dsi:         PASS -> DMESG-FAIL +1
    - {fi-kbl-7567u}:     SKIP -> DMESG-FAIL +1
    - fi-kbl-r:           PASS -> DMESG-FAIL +1

  * igt@kms_cursor_legacy@basic-flip-before-cursor-atomic:
    - fi-bxt-j4205:       PASS -> FAIL +1
    - fi-glk-j4005:       PASS -> FAIL +1
    - fi-cfl-8109u:       PASS -> FAIL +1
    - fi-whl-u:           PASS -> FAIL +1
    - fi-bxt-dsi:         PASS -> FAIL +1
    - fi-cfl-8700k:       PASS -> FAIL +1
    - fi-skl-iommu:       PASS -> FAIL +1
    - fi-kbl-x1275:       PASS -> FAIL +1

  * igt@kms_cursor_legacy@basic-flip-before-cursor-legacy:
    - fi-cfl-guc:         PASS -> FAIL +1
    - fi-glk-dsi:         NOTRUN -> FAIL +1
    - {fi-kbl-7567u}:     SKIP -> FAIL +1
    - fi-apl-guc:         PASS -> FAIL +1
    - fi-kbl-7560u:       PASS -> FAIL +1
    - fi-skl-6770hq:      PASS -> FAIL +2
    - fi-skl-6260u:       PASS -> FAIL +1
    - fi-skl-gvtdvm:      PASS -> FAIL +1
    - fi-kbl-r:           PASS -> FAIL +1

  
#### Warnings ####

  * igt@kms_pipe_crc_basic@nonblocking-crc-pipe-c:
    - {fi-kbl-7567u}:     SKIP -> PASS +29

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

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

### IGT changes ###

#### Issues hit ####

  * igt@amdgpu/amd_basic@cs-compute:
    - fi-kbl-8809g:       NOTRUN -> FAIL [fdo#108094]

  * igt@amdgpu/amd_prime@amd-to-i915:
    - fi-kbl-8809g:       NOTRUN -> FAIL [fdo#107341]

  * igt@i915_selftest@live_hangcheck:
    - fi-bwr-2160:        PASS -> DMESG-FAIL [fdo#108735]

  * igt@kms_chamelium@common-hpd-after-suspend:
    - fi-skl-6700k2:      PASS -> INCOMPLETE [fdo#104108] / [fdo#105524] / [k.org#199541]

  * igt@kms_cursor_legacy@basic-flip-before-cursor-atomic:
    - {fi-icl-u3}:        PASS -> FAIL [fdo#107736] +1

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

  
#### Possible fixes ####

  * igt@amdgpu/amd_basic@userptr:
    - fi-kbl-8809g:       DMESG-WARN -> PASS

  * igt@gem_ctx_create@basic-files:
    - fi-bsw-kefka:       FAIL [fdo#108656] -> PASS

  * igt@gem_mmap_gtt@basic-small-copy:
    - fi-glk-dsi:         INCOMPLETE [fdo#103359] / [k.org#198133] -> PASS

  * igt@kms_frontbuffer_tracking@basic:
    - fi-hsw-peppy:       DMESG-WARN [fdo#102614] -> PASS

  * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
    - fi-cfl-8109u:       INCOMPLETE [fdo#106070] / [fdo#108126] -> PASS

  
#### Warnings ####

  * igt@i915_selftest@live_contexts:
    - {fi-icl-u3}:        DMESG-FAIL [fdo#108569] -> INCOMPLETE [fdo#108315]

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

  [fdo#102614]: https://bugs.freedesktop.org/show_bug.cgi?id=102614
  [fdo#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359
  [fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
  [fdo#105524]: https://bugs.freedesktop.org/show_bug.cgi?id=105524
  [fdo#106070]: https://bugs.freedesktop.org/show_bug.cgi?id=106070
  [fdo#107341]: https://bugs.freedesktop.org/show_bug.cgi?id=107341
  [fdo#107736]: https://bugs.freedesktop.org/show_bug.cgi?id=107736
  [fdo#108094]: https://bugs.freedesktop.org/show_bug.cgi?id=108094
  [fdo#108126]: https://bugs.freedesktop.org/show_bug.cgi?id=108126
  [fdo#108315]: https://bugs.freedesktop.org/show_bug.cgi?id=108315
  [fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
  [fdo#108656]: https://bugs.freedesktop.org/show_bug.cgi?id=108656
  [fdo#108735]: https://bugs.freedesktop.org/show_bug.cgi?id=108735
  [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
  [k.org#199541]: https://bugzilla.kernel.org/show_bug.cgi?id=199541


Participating hosts (48 -> 42)
------------------------------

  Missing    (6): fi-ilk-m540 fi-hsw-4200u fi-skl-guc fi-byt-squawks fi-bsw-cyan fi-pnv-d510 


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

    * Linux: CI_DRM_5277 -> Patchwork_11038

  CI_DRM_5277: 13e7a0e59420cbdafca1cedbe2d9c136180aa689 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4743: edb2db2cf2b6665d7ba3fa9117263302f6307a4f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_11038: 193e7356179f4f20f01a3401bb1a1be712ef7910 @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

193e7356179f drm/i915: Switch to level-based DDB allocation algorithm
e52095e73e0d drm/i915: Don't use DDB allocation when choosing gen9 watermark method
2a7cd471873a drm/i915: Remove a very stale FIXME

== Logs ==

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

  parent reply	other threads:[~2018-12-06 17:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 17:09 [PATCH 0/3] New DDB allocation algorithm Matt Roper
2018-12-06 17:09 ` [PATCH 1/3] drm/i915: Remove a very stale FIXME Matt Roper
2018-12-10 19:34   ` Ville Syrjälä
2018-12-06 17:09 ` [PATCH 2/3] drm/i915: Don't use DDB allocation when choosing gen9 watermark method Matt Roper
2018-12-06 17:09 ` [PATCH 3/3] drm/i915: Switch to level-based DDB allocation algorithm Matt Roper
2018-12-06 23:55   ` [PATCH 3/3] drm/i915: Switch to level-based DDB allocation algorithm (v2) Matt Roper
2018-12-10 20:16     ` Ville Syrjälä
2018-12-06 17:18 ` ✗ Fi.CI.CHECKPATCH: warning for New DDB allocation algorithm Patchwork
2018-12-06 17:19 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-06 17:44 ` Patchwork [this message]
2018-12-07  0:23 ` ✗ Fi.CI.SPARSE: warning for New DDB allocation algorithm (rev2) Patchwork
2018-12-07  0:40 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-07 13:44 ` ✓ 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=20181206174459.2790.92570@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@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