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 drm/i915: Track vma activity per fence.context, not per engine (rev2)
Date: Fri, 29 Jun 2018 22:38:36 -0000 [thread overview]
Message-ID: <20180629223836.15408.4952@emeril.freedesktop.org> (raw)
In-Reply-To: <24ec4018c46bc7ee0d0b2afa1e855b1b9995e3f2>
== Series Details ==
Series: drm/i915: Track vma activity per fence.context, not per engine (rev2)
URL : https://patchwork.freedesktop.org/series/45480/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4408 -> Patchwork_9487 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/45480/revisions/2/mbox/
== Known issues ==
Here are the changes found in Patchwork_9487 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@kms_frontbuffer_tracking@basic:
fi-hsw-peppy: PASS -> DMESG-FAIL (fdo#106103, fdo#102614)
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
fi-bxt-dsi: NOTRUN -> INCOMPLETE (fdo#103927)
igt@prime_vgem@basic-fence-flip:
fi-ilk-650: PASS -> FAIL (fdo#104008)
==== Possible fixes ====
igt@gem_ringfill@basic-default-hang:
fi-bxt-dsi: INCOMPLETE (fdo#103927) -> PASS
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
{fi-cfl-8109u}: FAIL (fdo#103375) -> PASS
{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#103375 https://bugs.freedesktop.org/show_bug.cgi?id=103375
fdo#103927 https://bugs.freedesktop.org/show_bug.cgi?id=103927
fdo#104008 https://bugs.freedesktop.org/show_bug.cgi?id=104008
fdo#106103 https://bugs.freedesktop.org/show_bug.cgi?id=106103
== Participating hosts (45 -> 40) ==
Missing (5): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-hsw-4200u
== Build changes ==
* Linux: CI_DRM_4408 -> Patchwork_9487
CI_DRM_4408: 23ebdd88976b4fc81577ddce513c3f192620b3df @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4532: 840d12e2f050b784552197403d6575a57b6e896d @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9487: 26c316980c641ffcaa8cc634a2dd3b9ef6b0cb7d @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
26c316980c64 horror
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9487/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-06-29 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <24ec4018c46bc7ee0d0b2afa1e855b1b9995e3f2>
2018-06-29 22:00 ` [PATCH v2] horror Chris Wilson
2018-06-29 22:01 ` [PATCH v2] drm/i915: Track vma activity per fence.context, not per engine Chris Wilson
2018-06-29 22:18 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Track vma activity per fence.context, not per engine (rev2) Patchwork
2018-06-29 22:38 ` Patchwork [this message]
2018-06-30 1:30 ` ✓ Fi.CI.IGT: success " 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=20180629223836.15408.4952@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).