From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for drm/i915: Keep physical cursors pinned while in use
Date: Fri, 17 Aug 2018 11:04:05 -0000 [thread overview]
Message-ID: <20180817110405.21067.2098@emeril.freedesktop.org> (raw)
In-Reply-To: <20180817082405.755-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915: Keep physical cursors pinned while in use
URL : https://patchwork.freedesktop.org/series/48379/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4684_full -> Patchwork_9966_full =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork_9966_full need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_9966_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_9966_full:
=== IGT changes ===
==== Warnings ====
igt@gem_exec_params@dr1-dirt:
shard-kbl: PASS -> ( 2 PASS ) +842
igt@gem_exec_schedule@preempt-other-chain-blt:
shard-snb: SKIP -> ( 2 SKIP ) +1076
igt@gem_pwrite_pread@snooped-pwrite-blt-cpu_mmap-correctness:
shard-snb: PASS -> ( 2 PASS ) +1062
igt@gem_userptr_blits@map-fixed-invalidate-overlap:
shard-glk: PASS -> ( 2 PASS ) +1216
igt@kms_concurrent@pipe-d:
shard-hsw: SKIP -> ( 2 SKIP ) +584
igt@kms_flip@2x-plain-flip-ts-check:
shard-apl: SKIP -> ( 2 SKIP ) +516
igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-blt:
shard-glk: SKIP -> ( 2 SKIP ) +473
igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-wc:
shard-kbl: SKIP -> ( 2 SKIP ) +311
igt@kms_rotation_crc@sprite-rotation-90-pos-100-0:
shard-apl: PASS -> ( 2 PASS ) +1098
igt@pm_rc6_residency@rc6-accuracy:
shard-kbl: PASS -> ( 1 PASS, 1 SKIP )
igt@syncobj_basic@bad-create-flags:
shard-hsw: PASS -> ( 2 PASS ) +1107
== Known issues ==
Here are the changes found in Patchwork_9966_full that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_exec_schedule@pi-ringfull-blt:
shard-kbl: NOTRUN -> ( 2 FAIL ) (fdo#103158)
igt@gem_mocs_settings@mocs-rc6-bsd1:
shard-snb: SKIP -> ( 2 INCOMPLETE ) (fdo#105411)
igt@kms_setmode@basic:
shard-kbl: PASS -> FAIL (fdo#99912)
igt@kms_sysfs_edid_timing:
shard-kbl: NOTRUN -> ( 2 FAIL ) (fdo#100047)
igt@perf@polling:
shard-hsw: PASS -> ( 1 FAIL, 1 PASS ) (fdo#102252)
==== Possible fixes ====
igt@prime_vgem@basic-fence-flip:
shard-snb: FAIL (fdo#104008) -> ( 2 PASS )
==== Warnings ====
igt@gem_exec_schedule@pi-ringfull-bsd:
shard-glk: FAIL (fdo#103158) -> ( 2 FAIL ) (fdo#103158) +1
igt@gem_exec_schedule@pi-ringfull-render:
shard-apl: FAIL (fdo#103158) -> ( 2 FAIL ) (fdo#103158) +1
igt@gem_exec_schedule@pi-ringfull-vebox:
shard-kbl: FAIL (fdo#103158) -> ( 2 FAIL ) (fdo#103158)
igt@kms_available_modes_crc@available_mode_test_crc:
shard-hsw: FAIL (fdo#106641) -> ( 2 FAIL ) (fdo#106641)
shard-kbl: FAIL (fdo#106641) -> ( 2 FAIL ) (fdo#106641)
igt@kms_cursor_legacy@2x-long-nonblocking-modeset-vs-cursor-atomic:
shard-glk: FAIL (fdo#105454, fdo#106509) -> ( 2 FAIL ) (fdo#105454, fdo#106509)
igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic:
shard-glk: FAIL (fdo#105454) -> ( 1 FAIL, 1 PASS ) (fdo#105454, fdo#106509)
igt@kms_draw_crc@draw-method-xrgb8888-mmap-wc-ytiled:
shard-glk: FAIL (fdo#103184) -> ( 1 FAIL, 1 PASS ) (fdo#103184)
igt@kms_rotation_crc@primary-rotation-180:
shard-snb: FAIL (fdo#103925) -> ( 2 FAIL ) (fdo#103925)
igt@kms_setmode@basic:
shard-apl: FAIL (fdo#99912) -> ( 2 FAIL ) (fdo#99912)
shard-glk: FAIL (fdo#99912) -> ( 2 FAIL ) (fdo#99912)
shard-hsw: FAIL (fdo#99912) -> ( 2 FAIL ) (fdo#99912)
shard-snb: FAIL (fdo#99912) -> ( 2 FAIL ) (fdo#99912)
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
fdo#100047 https://bugs.freedesktop.org/show_bug.cgi?id=100047
fdo#102252 https://bugs.freedesktop.org/show_bug.cgi?id=102252
fdo#103158 https://bugs.freedesktop.org/show_bug.cgi?id=103158
fdo#103184 https://bugs.freedesktop.org/show_bug.cgi?id=103184
fdo#103925 https://bugs.freedesktop.org/show_bug.cgi?id=103925
fdo#104008 https://bugs.freedesktop.org/show_bug.cgi?id=104008
fdo#105411 https://bugs.freedesktop.org/show_bug.cgi?id=105411
fdo#105454 https://bugs.freedesktop.org/show_bug.cgi?id=105454
fdo#106509 https://bugs.freedesktop.org/show_bug.cgi?id=106509
fdo#106641 https://bugs.freedesktop.org/show_bug.cgi?id=106641
fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
== Participating hosts (5 -> 5) ==
No changes in participating hosts
== Build changes ==
* Linux: CI_DRM_4684 -> Patchwork_9966
CI_DRM_4684: bb1a6d0044581c5d8867afde39111ea4605c644d @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4604: 2a5777f8a694f1f8edcf021afb1ef36192c6762d @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9966: df341afb28f5bdd2eaa3eba5a15dc854d08474b5 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_9966/shards.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-08-17 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 8:24 [PATCH] drm/i915: Keep physical cursors pinned while in use Chris Wilson
2018-08-17 8:29 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-08-17 8:47 ` ✓ Fi.CI.BAT: success " Patchwork
2018-08-17 11:04 ` Patchwork [this message]
2018-08-22 12:35 ` [PATCH] " Ville Syrjälä
2018-08-31 7:57 ` Chris Wilson
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=20180817110405.21067.2098@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).