public inbox for intel-gfx@lists.freedesktop.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: ✓ Fi.CI.BAT: success for series starting with [1/4] dma-fence: Propagate errors to dma-fence-array container
Date: Sat, 10 Aug 2019 16:20:53 -0000	[thread overview]
Message-ID: <20190810162053.15913.66994@emeril.freedesktop.org> (raw)
In-Reply-To: <20190810153430.30636-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [1/4] dma-fence: Propagate errors to dma-fence-array container
URL   : https://patchwork.freedesktop.org/series/65027/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_6675 -> Patchwork_13962
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13962/

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

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

### IGT changes ###

#### Issues hit ####

  * igt@i915_module_load@reload:
    - fi-blb-e6850:       [PASS][1] -> [INCOMPLETE][2] ([fdo#107718])
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6675/fi-blb-e6850/igt@i915_module_load@reload.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13962/fi-blb-e6850/igt@i915_module_load@reload.html

  * igt@kms_busy@basic-flip-a:
    - fi-kbl-7567u:       [PASS][3] -> [SKIP][4] ([fdo#109271] / [fdo#109278]) +2 similar issues
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6675/fi-kbl-7567u/igt@kms_busy@basic-flip-a.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13962/fi-kbl-7567u/igt@kms_busy@basic-flip-a.html

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

  * igt@prime_vgem@basic-fence-flip:
    - fi-icl-u3:          [PASS][7] -> [DMESG-WARN][8] ([fdo#107724]) +1 similar issue
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6675/fi-icl-u3/igt@prime_vgem@basic-fence-flip.html
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13962/fi-icl-u3/igt@prime_vgem@basic-fence-flip.html

  
#### Possible fixes ####

  * igt@debugfs_test@read_all_entries:
    - fi-ilk-650:         [DMESG-WARN][9] ([fdo#106387]) -> [PASS][10]
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6675/fi-ilk-650/igt@debugfs_test@read_all_entries.html
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13962/fi-ilk-650/igt@debugfs_test@read_all_entries.html

  * igt@gem_exec_reloc@basic-cpu-read-noreloc:
    - fi-icl-u3:          [DMESG-WARN][11] ([fdo#107724]) -> [PASS][12] +1 similar issue
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6675/fi-icl-u3/igt@gem_exec_reloc@basic-cpu-read-noreloc.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13962/fi-icl-u3/igt@gem_exec_reloc@basic-cpu-read-noreloc.html

  
  [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
  [fdo#106387]: https://bugs.freedesktop.org/show_bug.cgi?id=106387
  [fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
  [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
  [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
  [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278


Participating hosts (54 -> 46)
------------------------------

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


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

  * CI: CI-20190529 -> None
  * Linux: CI_DRM_6675 -> Patchwork_13962

  CI-20190529: 20190529
  CI_DRM_6675: cfacb6e14c0b7fc929565f9876f204e325a71b13 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_5127: f43f5fa12ac1b93febfe3eeb9e9985f5f3e2eff0 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_13962: c522abf3342df26cefc038573afb9039c66542f8 @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

c522abf3342d dma-fence: Always execute signal callbacks
476f7f51e0c0 dma-fence: Refactor signaling for manual invocation
dcf1085c9b2f dma-fence: Report the composite sync_file status
ff8f4c9b5c1d dma-fence: Propagate errors to dma-fence-array container

== Logs ==

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

  parent reply	other threads:[~2019-08-10 16:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-10 15:34 [PATCH 1/4] dma-fence: Propagate errors to dma-fence-array container Chris Wilson
2019-08-10 15:34 ` [PATCH 2/4] dma-fence: Report the composite sync_file status Chris Wilson
2019-08-12  9:05   ` [Intel-gfx] " Matthew Auld
2019-08-10 15:34 ` [PATCH 3/4] dma-fence: Refactor signaling for manual invocation Chris Wilson
2019-08-12 14:34   ` Koenig, Christian
2019-08-12 14:43     ` Chris Wilson
2019-08-12 14:50       ` Koenig, Christian
2019-08-12 14:53         ` Chris Wilson
2019-08-13  6:59           ` Koenig, Christian
2019-08-13  8:25             ` Chris Wilson
2019-08-13  8:49               ` Koenig, Christian
2019-08-10 15:34 ` [PATCH 4/4] dma-fence: Always execute signal callbacks Chris Wilson
2019-08-11  9:01   ` Koenig, Christian
2019-08-11  9:15     ` [PATCH 5/4] dma-fence: Have dma_fence_signal call signal_locked Chris Wilson
2019-08-11 16:09       ` Koenig, Christian
2019-08-14 17:20       ` Daniel Vetter
2019-08-15 18:45         ` Chris Wilson
2019-08-15 18:48           ` Daniel Vetter
2019-08-15 19:03             ` Chris Wilson
2019-08-15 19:29               ` Chris Wilson
2019-08-16  7:58                 ` Koenig, Christian
2019-08-10 15:56 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] dma-fence: Propagate errors to dma-fence-array container Patchwork
2019-08-10 16:20 ` Patchwork [this message]
2019-08-11  8:34 ` ✓ Fi.CI.IGT: success " Patchwork
2019-08-11  8:58 ` [PATCH 1/4] " Koenig, Christian
2019-08-11 11:56   ` Chris Wilson
2019-08-11  9:21 ` ✗ Fi.CI.BAT: failure for series starting with [1/4] dma-fence: Propagate errors to dma-fence-array container (rev2) Patchwork
2019-08-11 12:02 ` ✗ Fi.CI.BAT: failure for series starting with [1/4] dma-fence: Propagate errors to dma-fence-array container (rev3) Patchwork
2019-08-11 12:09 ` [PATCH v3] dma-fence: Propagate errors to dma-fence-array container Chris Wilson
2019-08-11 12:20 ` ✗ Fi.CI.BAT: failure for series starting with [v3] dma-fence: Propagate errors to dma-fence-array container (rev4) Patchwork
2019-08-11 12:21 ` [PATCH v4] dma-fence: Propagate errors to dma-fence-array container Chris Wilson
2019-08-11 16:08   ` Koenig, Christian
2019-08-11 16:25     ` [PATCH v5] " Chris Wilson
2019-08-11 16:28       ` Koenig, Christian
2019-08-11 19:33   ` [PATCH v4] " kbuild test robot
2019-08-11 13:08 ` ✗ Fi.CI.BAT: failure for series starting with [v4] dma-fence: Propagate errors to dma-fence-array container (rev5) Patchwork
2019-08-11 16:38 ` ✗ Fi.CI.BAT: failure for series starting with [v5] dma-fence: Propagate errors to dma-fence-array container (rev6) Patchwork
2019-08-15 19:22 ` ✗ Fi.CI.BAT: failure for series starting with [v5] dma-fence: Propagate errors to dma-fence-array container (rev7) 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=20190810162053.15913.66994@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox