Intel-GFX Archive on 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: success for Restore workarounds after engine reset and unify their handling (rev4)
Date: Mon, 03 Dec 2018 13:36:17 -0000	[thread overview]
Message-ID: <20181203133617.3448.79610@emeril.freedesktop.org> (raw)
In-Reply-To: <20181203125014.3219-1-tvrtko.ursulin@linux.intel.com>

== Series Details ==

Series: Restore workarounds after engine reset and unify their handling (rev4)
URL   : https://patchwork.freedesktop.org/series/53313/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_5240 -> Patchwork_10998
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://patchwork.freedesktop.org/api/1.0/series/53313/revisions/4/mbox/

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

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

### IGT changes ###

#### Issues hit ####

  * igt@gem_exec_suspend@basic-s4-devices:
    - fi-ivb-3520m:       PASS -> FAIL [fdo#108880]

  
#### Warnings ####

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

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

  [fdo#108315]: https://bugs.freedesktop.org/show_bug.cgi?id=108315
  [fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
  [fdo#108880]: https://bugs.freedesktop.org/show_bug.cgi?id=108880


Participating hosts (47 -> 43)
------------------------------

  Additional (1): fi-pnv-d510 
  Missing    (5): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 


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

    * Linux: CI_DRM_5240 -> Patchwork_10998

  CI_DRM_5240: bc2afe004b92ad969d5fd89de9ccefbc3fcda688 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4736: 285ebfb3b7adc56586031afa5150c4e5ad40c229 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_10998: b6aae830b133fd829597a12caffe760e6c08ff44 @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

b6aae830b133 drm/i915: Trim unused workaround list entries
dea19ac0666f drm/i915: Fuse per-context workaround handling with the common framework
5118aae39798 drm/i915: Move register white-listing to the common workaround framework
5e2506a706bf drm/i915/selftests: Add tests for GT and engine workaround verification
21f44a8d57a8 drm/i915: Verify GT workaround state after GPU init
a814929884ca drm/i915: Introduce per-engine workarounds
2c7ee2141088 drm/i915: Record GT workarounds in a list

== Logs ==

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

  parent reply	other threads:[~2018-12-03 13:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 12:50 [PATCH v4 0/7] Restore workarounds after engine reset and unify their handling Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 1/7] drm/i915: Record GT workarounds in a list Tvrtko Ursulin
2018-12-03 12:53   ` Chris Wilson
2018-12-03 13:33   ` Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 2/7] drm/i915: Introduce per-engine workarounds Tvrtko Ursulin
2018-12-03 13:33   ` Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 3/7] drm/i915: Verify GT workaround state after GPU init Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 4/7] drm/i915/selftests: Add tests for GT and engine workaround verification Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 5/7] drm/i915: Move register white-listing to the common workaround framework Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 6/7] drm/i915: Fuse per-context workaround handling with the common framework Tvrtko Ursulin
2018-12-03 13:33   ` Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 7/7] drm/i915: Trim unused workaround list entries Tvrtko Ursulin
2018-12-03 12:52   ` Chris Wilson
2018-12-03 13:05 ` ✗ Fi.CI.CHECKPATCH: warning for Restore workarounds after engine reset and unify their handling (rev4) Patchwork
2018-12-03 13:08 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-03 13:36 ` Patchwork [this message]
2018-12-03 14:40 ` ✗ Fi.CI.CHECKPATCH: warning for Restore workarounds after engine reset and unify their handling (rev7) Patchwork
2018-12-03 14:43 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-03 14:56 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-12-03 17:23 ` ✗ Fi.CI.CHECKPATCH: warning for Restore workarounds after engine reset and unify their handling (rev8) Patchwork
2018-12-03 17:26 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-04  8:01 ` ✗ Fi.CI.CHECKPATCH: warning for Restore workarounds after engine reset and unify their handling (rev9) Patchwork
2018-12-04  8:04 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-04  8:22 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-04  8:41 ` ✓ Fi.CI.BAT: success for Restore workarounds after engine reset and unify their handling (rev8) Patchwork
2018-12-04 13:02   ` Tvrtko Ursulin
2018-12-04  9:42 ` ✓ Fi.CI.IGT: success for Restore workarounds after engine reset and unify their handling (rev9) Patchwork
2018-12-04 12:12   ` Chris Wilson

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=20181203133617.3448.79610@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox