From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [v3,1/6] drm/i915: Generate i915_params {} using a macro
Date: Mon, 06 Feb 2017 13:25:16 -0000 [thread overview]
Message-ID: <20170206132516.14898.8956@emeril.freedesktop.org> (raw)
In-Reply-To: <20170206095146.4943-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [v3,1/6] drm/i915: Generate i915_params {} using a macro
URL : https://patchwork.freedesktop.org/series/19149/
State : failure
== Summary ==
Series 19149v1 Series without cover letter
https://patchwork.freedesktop.org/api/1.0/series/19149/revisions/1/mbox/
Test drv_hangman:
Subgroup error-state-basic:
pass -> INCOMPLETE (fi-hsw-4770)
Test kms_force_connector_basic:
Subgroup force-connector-state:
pass -> DMESG-WARN (fi-snb-2520m)
Subgroup force-load-detect:
dmesg-warn -> PASS (fi-snb-2520m)
fi-bdw-5557u total:252 pass:214 dwarn:0 dfail:0 fail:0 skip:38
fi-bsw-n3050 total:252 pass:192 dwarn:0 dfail:0 fail:0 skip:60
fi-bxt-j4205 total:252 pass:208 dwarn:0 dfail:0 fail:0 skip:44
fi-bxt-t5700 total:209 pass:167 dwarn:0 dfail:0 fail:0 skip:41
fi-byt-j1900 total:252 pass:204 dwarn:0 dfail:0 fail:0 skip:48
fi-byt-n2820 total:252 pass:200 dwarn:0 dfail:0 fail:0 skip:52
fi-hsw-4770 total:5 pass:4 dwarn:0 dfail:0 fail:0 skip:0
fi-hsw-4770r total:252 pass:211 dwarn:0 dfail:0 fail:0 skip:41
fi-ilk-650 total:14 pass:11 dwarn:0 dfail:0 fail:0 skip:2
fi-ivb-3520m total:252 pass:210 dwarn:0 dfail:0 fail:0 skip:42
fi-ivb-3770 total:252 pass:210 dwarn:0 dfail:0 fail:0 skip:42
fi-kbl-7500u total:252 pass:207 dwarn:0 dfail:0 fail:2 skip:43
fi-skl-6260u total:252 pass:215 dwarn:0 dfail:0 fail:0 skip:37
fi-skl-6700hq total:252 pass:210 dwarn:0 dfail:0 fail:0 skip:42
fi-skl-6700k total:252 pass:205 dwarn:4 dfail:0 fail:0 skip:43
fi-skl-6770hq total:252 pass:215 dwarn:0 dfail:0 fail:0 skip:37
fi-snb-2520m total:252 pass:200 dwarn:1 dfail:0 fail:0 skip:51
fi-snb-2600 total:252 pass:200 dwarn:0 dfail:0 fail:0 skip:52
e7d4ec79b24f82431f34d070d16772538422fb13 drm-tip: 2017y-02m-06d-11h-49m-42s UTC integration manifest
48b227a drm/i915: The return of i915_gpu_info to debugfs
a0caf5d drm/i915: Add i915_param charp macro magic
6aef0eb drm/i915: Show the current i915_params in debugfs/i915_capabilites
7edf1c7 drm/i915: Capture module parameters for the GPU error state
66445eb drm/i915: Use bool i915_param.alpha_support
84d6a9c drm/i915: Generate i915_params {} using a macro
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_3708/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-02-06 13:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 9:51 [PATCH v3 1/6] drm/i915: Generate i915_params {} using a macro Chris Wilson
2017-02-06 9:51 ` [PATCH v3 2/6] drm/i915: Use bool i915_param.alpha_support Chris Wilson
2017-02-06 9:51 ` [PATCH v3 3/6] drm/i915: Capture module parameters for the GPU error state Chris Wilson
2017-02-06 11:13 ` Joonas Lahtinen
2017-02-06 11:24 ` Chris Wilson
2017-02-06 11:29 ` Chris Wilson
2017-02-06 9:51 ` [PATCH v3 4/6] drm/i915: Show the current i915_params in debugfs/i915_capabilites Chris Wilson
2017-02-06 11:21 ` Joonas Lahtinen
2017-02-06 9:51 ` [PATCH v3 5/6] drm/i915: Add i915_param charp macro magic Chris Wilson
2017-02-06 12:32 ` Joonas Lahtinen
2017-02-06 13:06 ` Chris Wilson
2017-02-07 9:12 ` Chris Wilson
2017-02-21 16:10 ` Jani Nikula
2017-02-21 16:26 ` [PATCH] " Chris Wilson
2017-02-22 10:06 ` Jani Nikula
2017-02-22 10:11 ` Chris Wilson
2017-02-22 10:29 ` Joonas Lahtinen
2017-02-22 10:33 ` Chris Wilson
2017-02-22 10:30 ` Jani Nikula
2017-02-22 10:37 ` Chris Wilson
2017-02-06 9:51 ` [PATCH v3 6/6] drm/i915: The return of i915_gpu_info to debugfs Chris Wilson
2017-02-07 9:09 ` Chris Wilson
2017-02-06 13:25 ` 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=20170206132516.14898.8956@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox