From: Patchwork <patchwork@emeril.freedesktop.org>
To: Tvrtko Ursulin <tursulin@ursulin.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for drm/i915: Engine discovery query (rev2)
Date: Wed, 11 Apr 2018 13:53:07 -0000 [thread overview]
Message-ID: <20180411135307.26761.45191@emeril.freedesktop.org> (raw)
In-Reply-To: <20180314140539.9287-1-tvrtko.ursulin@linux.intel.com>
== Series Details ==
Series: drm/i915: Engine discovery query (rev2)
URL : https://patchwork.freedesktop.org/series/39958/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4044_full -> Patchwork_8665_full =
== Summary - SUCCESS ==
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_8665/
== Known issues ==
Here are the changes found in Patchwork_8665_full that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@kms_flip@flip-vs-expired-vblank:
shard-hsw: PASS -> FAIL (fdo#105189)
igt@kms_flip@wf_vblank-ts-check:
shard-hsw: PASS -> FAIL (fdo#103928)
==== Possible fixes ====
igt@kms_flip@plain-flip-fb-recreate-interruptible:
shard-hsw: FAIL (fdo#100368) -> PASS
igt@kms_flip@wf_vblank-ts-check-interruptible:
shard-hsw: FAIL (fdo#103928) -> PASS +1
igt@kms_rotation_crc@primary-rotation-180:
shard-hsw: FAIL (fdo#103925) -> PASS
igt@kms_setmode@basic:
shard-kbl: FAIL (fdo#99912) -> PASS
igt@perf_pmu@busy-accuracy-50-bcs0:
shard-kbl: FAIL (fdo#105157) -> PASS
fdo#100368 https://bugs.freedesktop.org/show_bug.cgi?id=100368
fdo#103925 https://bugs.freedesktop.org/show_bug.cgi?id=103925
fdo#103928 https://bugs.freedesktop.org/show_bug.cgi?id=103928
fdo#105157 https://bugs.freedesktop.org/show_bug.cgi?id=105157
fdo#105189 https://bugs.freedesktop.org/show_bug.cgi?id=105189
fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
== Participating hosts (6 -> 4) ==
Missing (2): shard-glk shard-glkb
== Build changes ==
* Linux: CI_DRM_4044 -> Patchwork_8665
CI_DRM_4044: bb98639a2babe9d26edca8ea44c3e9f968c6c30f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4421: 27cd3793a3a183e4ec70c392f293e840642f2799 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_8665: 487fa7f5e720e1e791ab688204c0285a9270774d @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4421: 45e115f293fd6acc0c9647cf2d3b76be78819ba5 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_8665/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-04-11 13:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 14:05 [RFC] drm/i915: Engine discovery query Tvrtko Ursulin
2018-03-14 14:44 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-03-14 16:40 ` [RFC] " Lionel Landwerlin
2018-03-14 17:53 ` Tvrtko Ursulin
2018-03-14 17:58 ` Lionel Landwerlin
2018-03-14 18:18 ` Bloomfield, Jon
2018-03-14 19:34 ` ✓ Fi.CI.IGT: success for " Patchwork
2018-04-11 9:46 ` [RFC v2] " Tvrtko Ursulin
2018-04-11 16:32 ` Lionel Landwerlin
2018-04-16 10:11 ` Tvrtko Ursulin
2018-04-16 14:50 ` Lionel Landwerlin
2018-04-11 11:33 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Engine discovery query (rev2) Patchwork
2018-04-11 11:49 ` ✓ Fi.CI.BAT: success " Patchwork
2018-04-11 13:53 ` Patchwork [this message]
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=20180411135307.26761.45191@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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.