From: Jani Nikula <jani.nikula@intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm: Fix LSPCON kernel-doc (rev2)
Date: Wed, 19 Oct 2016 18:21:33 +0300 [thread overview]
Message-ID: <87pomwl5z6.fsf@intel.com> (raw)
In-Reply-To: <20161019145335.17804.86216@emeril.freedesktop.org>
On Wed, 19 Oct 2016, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: drm: Fix LSPCON kernel-doc (rev2)
> URL : https://patchwork.freedesktop.org/series/14017/
> State : failure
>
> == Summary ==
>
> Series 14017v2 drm: Fix LSPCON kernel-doc
> https://patchwork.freedesktop.org/api/1.0/series/14017/revisions/2/mbox/
>
> Test gem_exec_suspend:
> Subgroup basic-s3:
> incomplete -> PASS (fi-snb-2520m)
> fail -> DMESG-WARN (fi-ilk-650)
> Test kms_busy:
> Subgroup basic-flip-default-a:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup basic-flip-default-b:
> pass -> DMESG-WARN (fi-ilk-650)
> Test kms_cursor_legacy:
> Subgroup basic-busy-flip-before-cursor-legacy:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup basic-busy-flip-before-cursor-varying-size:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup basic-flip-after-cursor-legacy:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup basic-flip-after-cursor-varying-size:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup basic-flip-before-cursor-legacy:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup basic-flip-before-cursor-varying-size:
> pass -> DMESG-WARN (fi-ilk-650)
> Test kms_flip:
> Subgroup basic-flip-vs-dpms:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup basic-flip-vs-modeset:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup basic-flip-vs-wf_vblank:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup basic-plain-flip:
> pass -> DMESG-WARN (fi-ilk-650)
> Test kms_force_connector_basic:
> Subgroup force-load-detect:
> incomplete -> PASS (fi-ivb-3770)
> incomplete -> PASS (fi-byt-j1900)
> Test kms_pipe_crc_basic:
> Subgroup hang-read-crc-pipe-a:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup hang-read-crc-pipe-b:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup nonblocking-crc-pipe-a:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup nonblocking-crc-pipe-a-frame-sequence:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup nonblocking-crc-pipe-b:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup nonblocking-crc-pipe-b-frame-sequence:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup read-crc-pipe-a:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup read-crc-pipe-a-frame-sequence:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup read-crc-pipe-b:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup read-crc-pipe-b-frame-sequence:
> pass -> DMESG-WARN (fi-ilk-650)
> Subgroup suspend-read-crc-pipe-a:
> fail -> DMESG-WARN (fi-ilk-650)
> Subgroup suspend-read-crc-pipe-b:
> pass -> INCOMPLETE (fi-snb-2600)
> fail -> PASS (fi-ilk-650)
ilk on an underrun spree. Funny how a comments only change causes
that. :/
J.
>
> fi-bdw-5557u total:246 pass:231 dwarn:0 dfail:0 fail:0 skip:15
> fi-bsw-n3050 total:246 pass:203 dwarn:1 dfail:0 fail:0 skip:42
> fi-bxt-t5700 total:246 pass:216 dwarn:0 dfail:0 fail:0 skip:30
> fi-byt-j1900 total:246 pass:213 dwarn:1 dfail:0 fail:1 skip:31
> fi-byt-n2820 total:246 pass:209 dwarn:1 dfail:0 fail:1 skip:35
> fi-hsw-4770 total:246 pass:224 dwarn:0 dfail:0 fail:0 skip:22
> fi-hsw-4770r total:246 pass:223 dwarn:1 dfail:0 fail:0 skip:22
> fi-ilk-650 total:246 pass:160 dwarn:24 dfail:0 fail:2 skip:60
> fi-ivb-3520m total:246 pass:221 dwarn:0 dfail:0 fail:0 skip:25
> fi-ivb-3770 total:246 pass:221 dwarn:0 dfail:0 fail:0 skip:25
> fi-kbl-7200u total:246 pass:222 dwarn:0 dfail:0 fail:0 skip:24
> fi-skl-6260u total:246 pass:232 dwarn:0 dfail:0 fail:0 skip:14
> fi-skl-6700hq total:246 pass:222 dwarn:1 dfail:0 fail:0 skip:23
> fi-skl-6700k total:246 pass:221 dwarn:1 dfail:0 fail:0 skip:24
> fi-skl-6770hq total:246 pass:232 dwarn:0 dfail:0 fail:0 skip:14
> fi-snb-2520m total:246 pass:210 dwarn:0 dfail:0 fail:0 skip:36
> fi-snb-2600 total:209 pass:176 dwarn:0 dfail:0 fail:0 skip:32
>
> Results at /archive/results/CI_IGT_test/Patchwork_2760/
>
> d5cbeba648bec880aa0e1f7a531e684499a079a7 drm-intel-nightly: 2016y-10m-19d-11h-13m-08s UTC integration manifest
> 827d5ad drm: Fix LSPCON kernel-doc
>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-10-19 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 11:43 [PATCH] drm: Fix LSPCON kernel-doc Jani Nikula
2016-10-19 11:57 ` Ville Syrjälä
2016-10-19 12:08 ` Jani Nikula
2016-10-19 14:56 ` Ville Syrjälä
2016-10-19 15:22 ` Jani Nikula
2016-10-19 14:53 ` ✗ Fi.CI.BAT: failure for drm: Fix LSPCON kernel-doc (rev2) Patchwork
2016-10-19 15:21 ` Jani Nikula [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=87pomwl5z6.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.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