From: Jani Nikula <jani.nikula@linux.intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>,
Ramalingam C <ramalingam.c@intel.com>
Cc: "Sarvela, Tomi P" <tomi.p.sarvela@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: Sharing the pixel_format_from_vbt to whole i915
Date: Thu, 07 Apr 2016 15:58:12 +0300 [thread overview]
Message-ID: <87h9fdwp7f.fsf@intel.com> (raw)
In-Reply-To: <20160407120235.21338.74812@emeril.freedesktop.org>
On Thu, 07 Apr 2016, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: series starting with [1/2] drm/i915: Sharing the pixel_format_from_vbt to whole i915
> URL : https://patchwork.freedesktop.org/series/5405/
> State : failure
>
> == Summary ==
>
> Series 5405v1 Series without cover letter
> http://patchwork.freedesktop.org/api/1.0/series/5405/revisions/1/mbox/
>
> Test drv_hangman:
> Subgroup error-state-basic:
> fail -> PASS (ilk-hp8440p)
> Test drv_module_reload_basic:
> dmesg-warn -> PASS (bsw-nuc-2)
> Test gem_basic:
> Subgroup bad-close:
> dmesg-warn -> PASS (bsw-nuc-2)
> Subgroup create-close:
> dmesg-warn -> PASS (bsw-nuc-2)
> Test gem_ctx_create:
> Subgroup basic:
> pass -> DMESG-WARN (bsw-nuc-2)
> Test gem_ctx_param_basic:
> Subgroup invalid-param-set:
> pass -> DMESG-WARN (bsw-nuc-2)
> Subgroup non-root-set:
> dmesg-warn -> PASS (bsw-nuc-2)
> Subgroup non-root-set-no-zeromap:
> dmesg-warn -> PASS (bsw-nuc-2)
> Subgroup root-set:
> pass -> DMESG-WARN (bsw-nuc-2)
> Test gem_ctx_switch:
> Subgroup basic-default:
> pass -> SKIP (bsw-nuc-2)
> Test gem_exec_basic:
> Subgroup basic-blt:
> pass -> SKIP (bsw-nuc-2)
> Subgroup basic-render:
> skip -> PASS (bsw-nuc-2)
> Test gem_exec_suspend:
> Subgroup basic-s3:
> pass -> SKIP (bsw-nuc-2)
> Test gem_exec_whisper:
> Subgroup basic:
> skip -> PASS (bsw-nuc-2)
> Test gem_flink_basic:
> Subgroup basic:
> dmesg-warn -> PASS (bsw-nuc-2)
> Subgroup flink-lifetime:
> dmesg-warn -> PASS (bsw-nuc-2)
> Test gem_linear_blits:
> Subgroup basic:
> dmesg-fail -> PASS (bsw-nuc-2)
> Test gem_mmap_gtt:
> Subgroup basic-write-gtt:
> dmesg-warn -> PASS (bsw-nuc-2)
> Subgroup basic-write-read-distinct:
> pass -> DMESG-WARN (bsw-nuc-2)
> Test gem_pread:
> Subgroup basic:
> pass -> DMESG-WARN (bsw-nuc-2)
> Test gem_ringfill:
> Subgroup basic-default-hang:
> pass -> SKIP (bsw-nuc-2)
> Subgroup basic-default-interruptible:
> skip -> DMESG-FAIL (bsw-nuc-2)
> Test gem_sync:
> Subgroup basic-all:
> dmesg-fail -> PASS (bsw-nuc-2)
> Subgroup basic-bsd:
> skip -> PASS (bsw-nuc-2)
> Subgroup basic-default:
> skip -> PASS (bsw-nuc-2)
> Subgroup basic-render:
> incomplete -> PASS (bdw-nuci7) UNSTABLE
> Subgroup basic-vebox:
> skip -> PASS (bsw-nuc-2)
> Test gem_tiled_fence_blits:
> Subgroup basic:
> dmesg-fail -> PASS (bsw-nuc-2)
> Test kms_addfb_basic:
> Subgroup bad-pitch-256:
> pass -> DMESG-WARN (bsw-nuc-2)
> Subgroup bo-too-small-due-to-tiling:
> dmesg-warn -> PASS (bsw-nuc-2)
> Subgroup size-max:
> dmesg-warn -> PASS (bsw-nuc-2)
> Subgroup too-high:
> dmesg-warn -> PASS (bsw-nuc-2)
> Test kms_flip:
> Subgroup basic-flip-vs-modeset:
> dmesg-fail -> PASS (bsw-nuc-2)
> pass -> DMESG-WARN (ilk-hp8440p) UNSTABLE
> Subgroup basic-flip-vs-wf_vblank:
> pass -> FAIL (snb-x220t)
> Test kms_force_connector_basic:
> Subgroup force-connector-state:
> skip -> PASS (ivb-t430s)
> Subgroup prune-stale-modes:
> pass -> SKIP (ilk-hp8440p)
> Test kms_pipe_crc_basic:
> Subgroup hang-read-crc-pipe-b:
> pass -> DMESG-WARN (ilk-hp8440p)
> Test pm_rpm:
> Subgroup basic-rte:
> pass -> DMESG-WARN (byt-nuc) UNSTABLE
> Test prime_self_import:
> Subgroup basic-llseek-size:
> pass -> DMESG-WARN (bsw-nuc-2)
> Subgroup basic-with_one_bo_two_files:
> pass -> DMESG-WARN (bsw-nuc-2)
*sigh*, there's pretty much no way the patches could cause any of
this. :(
BR,
Jani.
>
> bdw-nuci7 total:196 pass:184 dwarn:0 dfail:0 fail:0 skip:12
> bdw-ultra total:196 pass:175 dwarn:0 dfail:0 fail:0 skip:21
> bsw-nuc-2 total:141 pass:80 dwarn:24 dfail:1 fail:0 skip:35
> byt-nuc total:196 pass:160 dwarn:1 dfail:0 fail:0 skip:35
> hsw-brixbox total:196 pass:174 dwarn:0 dfail:0 fail:0 skip:22
> hsw-gt2 total:196 pass:179 dwarn:0 dfail:0 fail:0 skip:17
> ilk-hp8440p total:196 pass:129 dwarn:2 dfail:0 fail:0 skip:65
> ivb-t430s total:196 pass:171 dwarn:0 dfail:0 fail:0 skip:25
> skl-i7k-2 total:196 pass:173 dwarn:0 dfail:0 fail:0 skip:23
> skl-nuci5 total:196 pass:185 dwarn:0 dfail:0 fail:0 skip:11
> snb-dellxps total:196 pass:162 dwarn:0 dfail:0 fail:0 skip:34
> snb-x220t total:196 pass:161 dwarn:0 dfail:0 fail:2 skip:33
>
> Results at /archive/results/CI_IGT_test/Patchwork_1825/
>
> 6b0bf94b75318abeab4c95fbf0507bc54d8959be drm-intel-nightly: 2016y-04m-07d-08h-29m-47s UTC integration manifest
> f61e309357f54fdc441fd20996225232627daa19 drm/i915/BXT: Get pipe conf from the port registers
> 81be0d7c63a7ef0c202434202d4f2982f5dcf304 drm/i915: Sharing the pixel_format_from_vbt to whole i915
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-07 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 9:06 [PATCH 1/2] drm/i915: Sharing the pixel_format_from_vbt to whole i915 Ramalingam C
2016-04-07 9:06 ` [PATCH 2/2] drm/i915/BXT: Get pipe conf from the port registers Ramalingam C
2016-04-07 13:52 ` Jani Nikula
2016-04-07 12:02 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: Sharing the pixel_format_from_vbt to whole i915 Patchwork
2016-04-07 12:58 ` Jani Nikula [this message]
2016-04-07 13:05 ` Tomi Sarvela
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=87h9fdwp7f.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.freedesktop.org \
--cc=ramalingam.c@intel.com \
--cc=tomi.p.sarvela@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 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.