From: Patchwork <patchwork@emeril.freedesktop.org>
To: tom.orourke@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for DO NOT MERGE: drm/i915: Enable GuC submission, where supported
Date: Thu, 07 Apr 2016 07:34:09 -0000 [thread overview]
Message-ID: <20160407073409.21339.66285@emeril.freedesktop.org> (raw)
In-Reply-To: <1459980553-116403-1-git-send-email-tom.orourke@intel.com>
== Series Details ==
Series: DO NOT MERGE: drm/i915: Enable GuC submission, where supported
URL : https://patchwork.freedesktop.org/series/5386/
State : failure
== Summary ==
Series 5386v1 DO NOT MERGE: drm/i915: Enable GuC submission, where supported
http://patchwork.freedesktop.org/api/1.0/series/5386/revisions/1/mbox/
Test gem_cpu_reloc:
Subgroup basic:
pass -> DMESG-FAIL (bsw-nuc-2)
Test gem_ctx_switch:
Subgroup basic-default:
pass -> DMESG-WARN (skl-nuci5)
pass -> DMESG-WARN (skl-i7k-2)
Test gem_exec_basic:
Subgroup basic-vebox:
pass -> SKIP (bsw-nuc-2)
Subgroup gtt-blt:
pass -> SKIP (bsw-nuc-2)
Test gem_exec_nop:
Subgroup basic:
pass -> SKIP (bsw-nuc-2)
Test gem_exec_suspend:
Subgroup basic-s3:
incomplete -> PASS (hsw-gt2)
Test gem_mmap_gtt:
Subgroup basic-small-bo:
pass -> DMESG-WARN (bsw-nuc-2)
Subgroup basic-small-bo-tiledx:
pass -> DMESG-WARN (bsw-nuc-2)
Subgroup basic-write-read:
pass -> DMESG-WARN (bsw-nuc-2)
Test gem_storedw_loop:
Subgroup basic-render:
pass -> INCOMPLETE (bsw-nuc-2)
Test gem_sync:
Subgroup basic-each:
pass -> DMESG-WARN (bsw-nuc-2)
Subgroup basic-render:
pass -> INCOMPLETE (bdw-nuci7) UNSTABLE
Test kms_addfb_basic:
Subgroup addfb25-yf-tiled:
pass -> DMESG-WARN (bsw-nuc-2)
Test kms_flip:
Subgroup basic-flip-vs-dpms:
dmesg-warn -> PASS (ilk-hp8440p) UNSTABLE
Subgroup basic-flip-vs-modeset:
pass -> DMESG-WARN (skl-i7k-2)
Subgroup basic-flip-vs-wf_vblank:
pass -> FAIL (byt-nuc)
Test kms_pipe_crc_basic:
Subgroup read-crc-pipe-c:
pass -> DMESG-WARN (bsw-nuc-2)
Subgroup suspend-read-crc-pipe-b:
pass -> SKIP (hsw-gt2)
bdw-nuci7 total:171 pass:162 dwarn:0 dfail:0 fail:0 skip:8
bdw-ultra total:196 pass:175 dwarn:0 dfail:0 fail:0 skip:21
bsw-nuc-2 total:178 pass:134 dwarn:6 dfail:1 fail:0 skip:36
byt-nuc total:196 pass:160 dwarn:0 dfail:0 fail:1 skip:35
hsw-gt2 total:196 pass:178 dwarn:0 dfail:0 fail:0 skip:18
ilk-hp8440p total:196 pass:132 dwarn:0 dfail:0 fail:0 skip:64
ivb-t430s total:196 pass:171 dwarn:0 dfail:0 fail:0 skip:25
skl-i7k-2 total:196 pass:171 dwarn:2 dfail:0 fail:0 skip:23
skl-nuci5 total:196 pass:184 dwarn:1 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:162 dwarn:0 dfail:0 fail:1 skip:33
BOOT FAILED for hsw-brixbox
Results at /archive/results/CI_IGT_test/Patchwork_1820/
c44bc2c9b26070f007fcff708589bf4631165644 drm-intel-nightly: 2016y-04m-06d-18h-03m-27s UTC integration manifest
5bc2d9e9595cefe0750639bf8e6bb5922eb50811 DO NOT MERGE: drm/i915: Enable GuC submission, where supported
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-04-07 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 22:09 [PATCH] DO NOT MERGE: drm/i915: Enable GuC submission, where supported tom.orourke
2016-04-07 7:34 ` Patchwork [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=20160407073409.21339.66285@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tom.orourke@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