From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [1/4] drm/i915: Enable transition watermarks for glk
Date: Mon, 4 Feb 2019 19:38:33 +0200 [thread overview]
Message-ID: <20190204173833.GJ20097@intel.com> (raw)
In-Reply-To: <20190131200735.16739.16409@emeril.freedesktop.org>
On Thu, Jan 31, 2019 at 08:07:35PM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [1/4] drm/i915: Enable transition watermarks for glk
> URL : https://patchwork.freedesktop.org/series/56025/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_5518_full -> Patchwork_12103_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_12103_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_12103_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_12103_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_cursor_legacy@2x-cursor-vs-flip-legacy:
> - shard-glk: PASS -> FAIL +2
(kms_cursor_legacy:2984) CRITICAL: Test assertion failure function two_screens_cursor_vs_flip, file ../tests/kms_cursor_legacy.c:1207:
(kms_cursor_legacy:2984) CRITICAL: Failed assertion: shared[child] > vrefresh[child]*target[child] / 2
(kms_cursor_legacy:2984) CRITICAL: completed 382 cursor updated in a period of 30 flips, we expect to complete approximately 3840 updates, with the threshold set at 1920
Subtest 2x-cursor-vs-flip-legacy failed.
2x-cursor-vs-flip-atomic and 2x-long-cursor-vs-flip-atomic also flipped
to fail but that fact is not reflected here for some reason.
Anyways, this failure doesn't seem directly related to watermarks.
>
>
> Known issues
> ------------
>
> Here are the changes found in Patchwork_12103_full that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@gem_exec_schedule@pi-ringfull-render:
> - shard-apl: NOTRUN -> FAIL [fdo#103158]
>
> * igt@gem_ppgtt@blt-vs-render-ctx0:
> - shard-glk: PASS -> DMESG-WARN [fdo#105763] / [fdo#106538]
>
> * igt@kms_cursor_crc@cursor-64x64-suspend:
> - shard-glk: PASS -> INCOMPLETE [fdo#103359] / [k.org#198133]
>
> * igt@kms_plane_multiple@atomic-pipe-a-tiling-none:
> - shard-apl: NOTRUN -> FAIL [fdo#103166]
>
> * igt@kms_plane_multiple@atomic-pipe-a-tiling-x:
> - shard-apl: PASS -> FAIL [fdo#103166]
> - shard-glk: PASS -> FAIL [fdo#103166]
>
>
> #### Possible fixes ####
>
> * igt@gem_eio@reset-stress:
> - shard-hsw: INCOMPLETE [fdo#103540] / [fdo#109482] -> PASS
>
> * igt@gem_workarounds@suspend-resume:
> - shard-kbl: INCOMPLETE [fdo#103665] -> PASS
>
> * igt@kms_busy@extended-pageflip-modeset-hang-oldfb-render-c:
> - shard-apl: DMESG-WARN [fdo#107956] -> PASS
>
> * igt@kms_color@pipe-b-ctm-max:
> - shard-apl: FAIL [fdo#108147] -> PASS
>
> * igt@kms_cursor_crc@cursor-256x256-suspend:
> - shard-hsw: INCOMPLETE [fdo#103540] -> PASS
>
> * igt@kms_flip@flip-vs-blocking-wf-vblank:
> - shard-snb: DMESG-WARN [fdo#107469] -> PASS
>
> * igt@kms_flip@flip-vs-panning-interruptible:
> - shard-hsw: DMESG-WARN [fdo#102614] -> PASS
>
> * igt@kms_plane@plane-position-covered-pipe-c-planes:
> - shard-apl: FAIL [fdo#103166] -> PASS +1
>
> * igt@kms_plane_multiple@atomic-pipe-a-tiling-yf:
> - shard-glk: FAIL [fdo#103166] -> PASS
>
> * igt@kms_setmode@basic:
> - shard-apl: FAIL [fdo#99912] -> PASS
>
> * igt@pm_rc6_residency@rc6-accuracy:
> - shard-snb: {SKIP} [fdo#109271] -> PASS
>
> * igt@sw_sync@sync_busy_fork:
> - shard-snb: INCOMPLETE [fdo#105411] -> PASS +1
>
>
> #### Warnings ####
>
> * igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-b:
> - shard-snb: {SKIP} [fdo#109271] / [fdo#109278] -> DMESG-WARN [fdo#107956]
>
>
> {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#103158]: https://bugs.freedesktop.org/show_bug.cgi?id=103158
> [fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
> [fdo#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359
> [fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540
> [fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
> [fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411
> [fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763
> [fdo#106538]: https://bugs.freedesktop.org/show_bug.cgi?id=106538
> [fdo#107469]: https://bugs.freedesktop.org/show_bug.cgi?id=107469
> [fdo#107956]: https://bugs.freedesktop.org/show_bug.cgi?id=107956
> [fdo#108147]: https://bugs.freedesktop.org/show_bug.cgi?id=108147
> [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
> [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
> [fdo#109482]: https://bugs.freedesktop.org/show_bug.cgi?id=109482
> [fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912
> [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
>
>
> Participating hosts (7 -> 5)
> ------------------------------
>
> Missing (2): shard-skl shard-iclb
>
>
> Build changes
> -------------
>
> * Linux: CI_DRM_5518 -> Patchwork_12103
>
> CI_DRM_5518: 2369fd28d3a46b865f6d4f1d309a4c6b7b4e6d93 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_4801: 6f6bacf12759fb319ade3ba37861ae711f8a5cd9 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_12103: 70785cf59b0d35fc4508bdb6b2e98c71435fedaf @ 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_12103/
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-04 17:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 7:42 [PATCH 1/4] drm/i915: Enable transition watermarks for glk Ville Syrjala
2019-01-31 7:42 ` [PATCH 2/4] drm/i915: Implement display w/a 1140 for glk/cnl Ville Syrjala
2019-01-31 18:07 ` Rodrigo Vivi
2019-01-31 7:42 ` [PATCH 3/4] drm/i915: Document that we implement WaIncreaseLatencyIPCEnabled Ville Syrjala
2019-01-31 18:08 ` Rodrigo Vivi
2019-01-31 7:42 ` [PATCH 4/4] drm/i915: Drop WaIncreaseLatencyIPCEnabled/1140 for cnl Ville Syrjala
2019-01-31 18:10 ` Rodrigo Vivi
2019-02-04 17:40 ` Ville Syrjälä
2019-02-04 17:49 ` Rodrigo Vivi
2019-02-04 17:58 ` Ville Syrjälä
2019-01-31 9:11 ` ✓ Fi.CI.BAT: success for series starting with [1/4] drm/i915: Enable transition watermarks for glk Patchwork
2019-01-31 18:04 ` [PATCH 1/4] " Rodrigo Vivi
2019-01-31 20:07 ` ✗ Fi.CI.IGT: failure for series starting with [1/4] " Patchwork
2019-02-04 17:38 ` Ville Syrjälä [this message]
2019-02-05 11:39 ` Petri Latvala
2019-02-05 19:34 ` ✗ Fi.CI.BAT: failure for series starting with [1/4] drm/i915: Enable transition watermarks for glk (rev2) 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=20190204173833.GJ20097@intel.com \
--to=ville.syrjala@linux.intel.com \
--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 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.