public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
	Patchwork <patchwork@emeril.freedesktop.org>,
	Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
Subject: Re: ✗ Fi.CI.IGT: failure for Add XYUV format support (rev6)
Date: Fri, 7 Sep 2018 18:21:21 +0300	[thread overview]
Message-ID: <043f32a1-752a-022a-68a9-45d2297665d9@linux.intel.com> (raw)
In-Reply-To: <20180907113722.6601.73016@emeril.freedesktop.org>



On 07/09/2018 14:37, Patchwork wrote:
> == Series Details ==
> 
> Series: Add XYUV format support (rev6)
> URL   : https://patchwork.freedesktop.org/series/48007/
> State : failure
> 
> == Summary ==
> 
> = CI Bug Log - changes from CI_DRM_4786_full -> Patchwork_10123_full =
> 
> == Summary - FAILURE ==
> 
>   Serious unknown changes coming with Patchwork_10123_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_10123_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_10123_full:
> 
>   === IGT changes ===
> 
>     ==== Possible regressions ====
> 
>     igt@kms_available_modes_crc@available_mode_test_crc:
>       shard-apl:          PASS -> FAIL
> 

This is known issue: https://bugs.freedesktop.org/show_bug.cgi?id=106701

That means your patch is a SUCCESS from a CI perspective. Sorry for the
noise!

>     
>     ==== Warnings ====
> 
>     igt@kms_cursor_legacy@cursora-vs-flipb-toggle:
>       shard-hsw:          SKIP -> PASS
> 
>     igt@kms_vblank@pipe-b-wait-forked:
>       shard-snb:          PASS -> SKIP
> 
>     igt@perf_pmu@rc6:
>       shard-kbl:          PASS -> SKIP
> 
>     
> == Known issues ==
> 
>   Here are the changes found in Patchwork_10123_full that come from known issues:
> 
>   === IGT changes ===
> 
>     ==== Issues hit ====
> 
>     igt@drv_suspend@shrink:
>       shard-glk:          PASS -> FAIL (fdo#106886)
> 
>     igt@gem_exec_big:
>       shard-hsw:          PASS -> INCOMPLETE (fdo#103540)
> 
>     
>     ==== Possible fixes ====
> 
>     igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-gtt:
>       shard-glk:          FAIL (fdo#103167) -> PASS
> 
>     igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-wc:
>       shard-apl:          FAIL (fdo#103167) -> PASS
> 
>     
>   fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
>   fdo#103540 https://bugs.freedesktop.org/show_bug.cgi?id=103540
>   fdo#106886 https://bugs.freedesktop.org/show_bug.cgi?id=106886
> 
> 
> == Participating hosts (5 -> 5) ==
> 
>   No changes in participating hosts
> 
> 
> == Build changes ==
> 
>     * Linux: CI_DRM_4786 -> Patchwork_10123
> 
>   CI_DRM_4786: d28dcb05a3c33df6fcb0828d81fa0bb6591a97be @ git://anongit.freedesktop.org/gfx-ci/linux
>   IGT_4634: 7d89cc39dde3b4881d85ace45d504cc098fa3684 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>   Patchwork_10123: 43038ad4912e589e9c487d88f4901c064ea66af4 @ 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_10123/shards.html
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-09-07 15:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07  8:45 [PATCH v10 0/2] Add XYUV format support Stanislav Lisovskiy
2018-09-07  8:45 ` [PATCH v10 1/2] drm: Introduce new DRM_FORMAT_XYUV Stanislav Lisovskiy
2018-09-07  8:45 ` [PATCH v10 2/2] drm/i915: Adding YUV444 packed format support for skl+ Stanislav Lisovskiy
2018-09-07  9:00 ` ✗ Fi.CI.CHECKPATCH: warning for Add XYUV format support (rev6) Patchwork
2018-09-07  9:23 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-07 11:37 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-09-07 15:21   ` Martin Peres [this message]
2018-09-10  7:38     ` Lisovskiy, Stanislav
2018-09-12 13:29 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-12 18:55 ` ✓ Fi.CI.IGT: " Patchwork
2018-09-14 13:36 ` [PATCH v10 0/2] Add XYUV format support Lisovskiy, Stanislav
2018-09-14 13:47   ` Ville Syrjälä
2018-09-14 14:30     ` Lisovskiy, Stanislav
2018-09-14 14:34       ` Saarinen, Jani
2018-09-14 14:49         ` [Intel-gfx] " Lisovskiy, Stanislav
2018-09-14 14:59           ` Alexandru-Cosmin Gheorghe
2018-09-17  8:27             ` [Intel-gfx] " Lisovskiy, Stanislav
2018-09-17  8:49               ` Alexandru-Cosmin Gheorghe
2018-09-14 17:05       ` Juha-Pekka Heikkilä
2018-09-17  8:25         ` [Intel-gfx] " Lisovskiy, Stanislav
2018-09-17  8:51           ` Juha-Pekka Heikkila

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=043f32a1-752a-022a-68a9-45d2297665d9@linux.intel.com \
    --to=martin.peres@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=patchwork@emeril.freedesktop.org \
    --cc=stanislav.lisovskiy@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