All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Check for error before calling cmpxchg()
Date: Fri, 06 Dec 2019 16:51:27 -0000	[thread overview]
Message-ID: <157565108723.31672.8851039706743753822@emeril.freedesktop.org> (raw)
In-Reply-To: <20191206160428.1503343-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [1/3] drm/i915: Check for error before calling cmpxchg()
URL   : https://patchwork.freedesktop.org/series/70568/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_7500 -> Patchwork_15630
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15630/index.html

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

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

### IGT changes ###

#### Issues hit ####

  * igt@i915_selftest@live_blt:
    - fi-bsw-n3050:       [PASS][1] -> [DMESG-FAIL][2] ([i915#723])
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7500/fi-bsw-n3050/igt@i915_selftest@live_blt.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15630/fi-bsw-n3050/igt@i915_selftest@live_blt.html

  * igt@i915_selftest@live_gem_contexts:
    - fi-hsw-peppy:       [PASS][3] -> [INCOMPLETE][4] ([i915#694])
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7500/fi-hsw-peppy/igt@i915_selftest@live_gem_contexts.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15630/fi-hsw-peppy/igt@i915_selftest@live_gem_contexts.html

  
#### Possible fixes ####

  * igt@gem_exec_parallel@basic:
    - {fi-tgl-u}:         [INCOMPLETE][5] ([i915#476]) -> [PASS][6]
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7500/fi-tgl-u/igt@gem_exec_parallel@basic.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15630/fi-tgl-u/igt@gem_exec_parallel@basic.html

  * igt@i915_selftest@live_gem_contexts:
    - fi-byt-j1900:       [DMESG-FAIL][7] ([i915#722]) -> [PASS][8]
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7500/fi-byt-j1900/igt@i915_selftest@live_gem_contexts.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15630/fi-byt-j1900/igt@i915_selftest@live_gem_contexts.html

  
#### Warnings ####

  * igt@runner@aborted:
    - fi-icl-u2:          [FAIL][9] ([fdo#110676] / [fdo#111093] / [k.org#202973]) -> [FAIL][10] ([fdo#111093])
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7500/fi-icl-u2/igt@runner@aborted.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15630/fi-icl-u2/igt@runner@aborted.html

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

  [fdo#110676]: https://bugs.freedesktop.org/show_bug.cgi?id=110676
  [fdo#111093]: https://bugs.freedesktop.org/show_bug.cgi?id=111093
  [i915#476]: https://gitlab.freedesktop.org/drm/intel/issues/476
  [i915#694]: https://gitlab.freedesktop.org/drm/intel/issues/694
  [i915#710]: https://gitlab.freedesktop.org/drm/intel/issues/710
  [i915#722]: https://gitlab.freedesktop.org/drm/intel/issues/722
  [i915#723]: https://gitlab.freedesktop.org/drm/intel/issues/723
  [k.org#202973]: https://bugzilla.kernel.org/show_bug.cgi?id=202973


Participating hosts (41 -> 33)
------------------------------

  Missing    (8): fi-hsw-4770r fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus 


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

  * CI: CI-20190529 -> None
  * Linux: CI_DRM_7500 -> Patchwork_15630

  CI-20190529: 20190529
  CI_DRM_7500: ccec746805883b1cc52d4d7af0e2f2612b6e6993 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_5334: 343aae776a58a67fa153825385e6fe90e3185c5b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_15630: 0cdafd401ba614bb0a896d7f7063535c5128ee85 @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

0cdafd401ba6 drm/i915: Propagate errors on awaiting already signaled dma-fences
da3cdaa0cab5 drm/i915: Propagate errors on awaiting already signaled fences
466638a1b768 drm/i915: Check for error before calling cmpxchg()

== Logs ==

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

  parent reply	other threads:[~2019-12-06 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 16:04 [Intel-gfx] [PATCH 1/3] drm/i915: Check for error before calling cmpxchg() Chris Wilson
2019-12-06 16:04 ` [Intel-gfx] [PATCH 2/3] drm/i915: Propagate errors on awaiting already signaled fences Chris Wilson
2019-12-06 16:04 ` [Intel-gfx] [PATCH 3/3] drm/i915: Propagate errors on awaiting already signaled dma-fences Chris Wilson
2019-12-06 16:51 ` Patchwork [this message]
2019-12-06 18:54 ` [Intel-gfx] [PATCH 1/3] drm/i915: Check for error before calling cmpxchg() Matthew Auld
2019-12-07  5:54 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/3] " 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=157565108723.31672.8851039706743753822@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --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 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.