From: Imre Deak <imre.deak@intel.com>
To: intel-gfx@lists.freedesktop.org,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
ronald@innovation.ch,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>
Subject: Re: ✓ Fi.CI.IGT: success for drm/i915/gen9+: Fix initial readout for Y tiled framebuffers
Date: Wed, 17 Oct 2018 13:50:10 +0300 [thread overview]
Message-ID: <20181017105010.GA714@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <20181016212605.2709.92586@emeril.freedesktop.org>
On Tue, Oct 16, 2018 at 09:26:05PM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/gen9+: Fix initial readout for Y tiled framebuffers
> URL : https://patchwork.freedesktop.org/series/51075/
> State : success
Pushed to -dinq, thanks for the report, review and testing.
>
> == Summary ==
>
> = CI Bug Log - changes from CI_DRM_4990_full -> Patchwork_10477_full =
>
> == Summary - SUCCESS ==
>
> No regressions found.
>
>
>
> == Known issues ==
>
> Here are the changes found in Patchwork_10477_full that come from known issues:
>
> === IGT changes ===
>
> ==== Issues hit ====
>
> igt@gem_exec_await@wide-contexts:
> shard-skl: PASS -> FAIL (fdo#106680)
>
> igt@gem_ppgtt@blt-vs-render-ctxn:
> shard-skl: NOTRUN -> TIMEOUT (fdo#108039)
>
> igt@kms_atomic_transition@1x-modeset-transitions-nonblocking:
> shard-skl: NOTRUN -> FAIL (fdo#108228)
>
> igt@kms_busy@extended-modeset-hang-newfb-render-a:
> shard-skl: NOTRUN -> DMESG-WARN (fdo#107956) +1
>
> igt@kms_busy@extended-pageflip-modeset-hang-oldfb-render-a:
> shard-glk: NOTRUN -> DMESG-WARN (fdo#107956)
>
> igt@kms_busy@extended-pageflip-modeset-hang-oldfb-render-b:
> shard-hsw: NOTRUN -> DMESG-WARN (fdo#107956) +2
>
> igt@kms_cursor_crc@cursor-256x256-suspend:
> shard-skl: NOTRUN -> FAIL (fdo#103191, fdo#103232)
>
> igt@kms_cursor_crc@cursor-256x85-sliding:
> shard-apl: PASS -> FAIL (fdo#103232)
>
> igt@kms_cursor_crc@cursor-64x64-suspend:
> shard-skl: PASS -> INCOMPLETE (fdo#104108)
>
> igt@kms_draw_crc@draw-method-xrgb2101010-pwrite-untiled:
> shard-skl: NOTRUN -> FAIL (fdo#103184) +2
>
> igt@kms_flip@blocking-absolute-wf_vblank:
> shard-kbl: PASS -> DMESG-WARN (fdo#105345)
>
> igt@kms_flip@flip-vs-expired-vblank-interruptible:
> shard-skl: PASS -> FAIL (fdo#105363)
>
> igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-onoff:
> shard-skl: NOTRUN -> FAIL (fdo#105682) +1
>
> igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-move:
> shard-skl: NOTRUN -> FAIL (fdo#103167) +4
>
> igt@kms_plane_alpha_blend@pipe-b-constant-alpha-max:
> shard-glk: NOTRUN -> FAIL (fdo#108145) +1
>
> igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
> shard-skl: NOTRUN -> FAIL (fdo#108145) +3
>
> igt@kms_setmode@basic:
> shard-apl: PASS -> FAIL (fdo#99912)
>
> igt@pm_rpm@gem-mmap-cpu:
> shard-skl: PASS -> INCOMPLETE (fdo#107807)
>
>
> ==== Possible fixes ====
>
> igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-wc:
> shard-glk: FAIL (fdo#103167) -> PASS
>
>
> fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
> fdo#103184 https://bugs.freedesktop.org/show_bug.cgi?id=103184
> fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
> fdo#103232 https://bugs.freedesktop.org/show_bug.cgi?id=103232
> fdo#104108 https://bugs.freedesktop.org/show_bug.cgi?id=104108
> fdo#105345 https://bugs.freedesktop.org/show_bug.cgi?id=105345
> fdo#105363 https://bugs.freedesktop.org/show_bug.cgi?id=105363
> fdo#105682 https://bugs.freedesktop.org/show_bug.cgi?id=105682
> fdo#106680 https://bugs.freedesktop.org/show_bug.cgi?id=106680
> fdo#107807 https://bugs.freedesktop.org/show_bug.cgi?id=107807
> fdo#107956 https://bugs.freedesktop.org/show_bug.cgi?id=107956
> fdo#108039 https://bugs.freedesktop.org/show_bug.cgi?id=108039
> fdo#108145 https://bugs.freedesktop.org/show_bug.cgi?id=108145
> fdo#108228 https://bugs.freedesktop.org/show_bug.cgi?id=108228
> fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
>
>
> == Participating hosts (6 -> 6) ==
>
> No changes in participating hosts
>
>
> == Build changes ==
>
> * Linux: CI_DRM_4990 -> Patchwork_10477
>
> CI_DRM_4990: 0bd34d92e9a27784cb988a300619f497ca0e99ec @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_4681: 959d6f95cb1344e0c0dace5b236e17755826fac1 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_10477: 030f7e7d682d65b11f75afd2a5e128e2b839130c @ 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_10477/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-10-17 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 16:00 [PATCH] drm/i915/gen9+: Fix initial readout for Y tiled framebuffers Imre Deak
2018-10-16 17:16 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-10-16 17:34 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-16 17:56 ` [PATCH] " Ville Syrjälä
2018-10-16 21:26 ` ✓ Fi.CI.IGT: success for " Patchwork
2018-10-17 10:50 ` Imre Deak [this message]
2018-10-17 9:02 ` [PATCH] " Life is hard, and then you die
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=20181017105010.GA714@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.westerberg@linux.intel.com \
--cc=ronald@innovation.ch \
--cc=ville.syrjala@linux.intel.com \
/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