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/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2)
Date: Fri, 06 Jul 2018 15:21:19 -0000 [thread overview]
Message-ID: <20180706152119.22157.67257@emeril.freedesktop.org> (raw)
In-Reply-To: <20180706103947.15919-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2)
URL : https://patchwork.freedesktop.org/series/46067/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4446 -> Patchwork_9568 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/46067/revisions/2/mbox/
== Known issues ==
Here are the changes found in Patchwork_9568 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@prime_vgem@basic-fence-flip:
fi-ilk-650: PASS -> FAIL (fdo#104008)
fdo#104008 https://bugs.freedesktop.org/show_bug.cgi?id=104008
== Participating hosts (47 -> 42) ==
Missing (5): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-hsw-4200u
== Build changes ==
* Linux: CI_DRM_4446 -> Patchwork_9568
CI_DRM_4446: 95944426a9ffda186843c78f2f925494e1bc53c5 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4543: 366eed37c7c71217e1cb1f3be5e26358a41f0001 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9568: a65a91a8871c69c8a80db2a1da700aaa4eb113b4 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
a65a91a8871c drm/i915: Track the last-active inside the i915_vma
42d0e21316dd drm/i915: Track vma activity per fence.context, not per engine
78318c338989 drm/i915: Move i915_vma_move_to_active() to i915_vma.c
39fbb254f607 drm/i915: Start returning an error from i915_vma_move_to_active()
951d50a80f49 drm/i915: Export i915_request_skip()
c404016bcc1d drm/i915: Refactor export_fence() after i915_vma_move_to_active()
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9568/issues.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-06 15:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 10:39 [PATCH 1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() Chris Wilson
2018-07-06 10:39 ` [PATCH 2/6] drm/i915: Export i915_request_skip() Chris Wilson
2018-07-06 10:39 ` [PATCH 3/6] drm/i915: Start returning an error from i915_vma_move_to_active() Chris Wilson
2018-07-06 10:39 ` [PATCH 4/6] drm/i915: Move i915_vma_move_to_active() to i915_vma.c Chris Wilson
2018-07-06 10:39 ` [PATCH 5/6] drm/i915: Track vma activity per fence.context, not per engine Chris Wilson
2018-07-06 10:39 ` [PATCH 6/6] drm/i915: Track the last-active inside the i915_vma Chris Wilson
2018-07-06 11:07 ` Tvrtko Ursulin
2018-07-06 12:31 ` [PATCH v5] " Chris Wilson
2018-07-06 12:02 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() Patchwork
2018-07-06 12:05 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-07-06 12:20 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-07-06 12:25 ` Chris Wilson
2018-07-06 15:05 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2) Patchwork
2018-07-06 15:08 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-07-06 15:21 ` Patchwork [this message]
2018-07-07 11:30 ` ✓ Fi.CI.IGT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2018-06-29 22:54 [PATCH 1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() Chris Wilson
2018-07-04 9:07 ` ✓ Fi.CI.BAT: success for series starting with [1/6] drm/i915: Refactor export_fence() after i915_vma_move_to_active() (rev2) 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=20180706152119.22157.67257@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;
as well as URLs for NNTP newsgroup(s).