From: Daniel Vetter <daniel@ffwll.ch>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with [v4,1/3] drm/edid: Add drm_edid_get_monitor_name()
Date: Fri, 15 Apr 2016 14:37:28 +0200 [thread overview]
Message-ID: <20160415123728.GV2510@phenom.ffwll.local> (raw)
In-Reply-To: <20160415062618.18151.27275@emeril.freedesktop.org>
On Fri, Apr 15, 2016 at 06:26:18AM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [v4,1/3] drm/edid: Add drm_edid_get_monitor_name()
> URL : https://patchwork.freedesktop.org/series/5731/
> State : failure
>
> == Summary ==
>
> Series 5731v1 Series without cover letter
> http://patchwork.freedesktop.org/api/1.0/series/5731/revisions/1/mbox/
>
>
> bdw-ultra total:203 pass:179 dwarn:0 dfail:0 fail:1 skip:23
> bsw-nuc-2 total:202 pass:162 dwarn:0 dfail:0 fail:1 skip:39
> byt-nuc total:202 pass:164 dwarn:0 dfail:0 fail:0 skip:38
> hsw-brixbox total:203 pass:178 dwarn:0 dfail:0 fail:1 skip:24
> ivb-t430s total:203 pass:174 dwarn:0 dfail:0 fail:1 skip:28
> skl-i7k-2 total:203 pass:177 dwarn:0 dfail:0 fail:1 skip:25
> skl-nuci5 total:203 pass:191 dwarn:0 dfail:0 fail:1 skip:11
> snb-dellxps total:203 pass:164 dwarn:0 dfail:0 fail:1 skip:38
> snb-x220t total:203 pass:164 dwarn:0 dfail:0 fail:2 skip:37
> BOOT FAILED for ilk-hp8440p
Discussed with Tomi, this box isn't wired up with a reset switch and
therefore can die on unrelated bad kernels. Without CI being able to
figure this out.
So should be fairly safe to ignore (but I'm not really happy that we don't
have more reliable information).
Applied all 3 patches to drm-misc, for easier merging.
-Daniel
>
> Results at /archive/results/CI_IGT_test/Patchwork_1905/
>
> c7583aec08ba04e2336bd9879a10f30d4e0cdc60 drm-intel-nightly: 2016y-04m-14d-14h-53m-34s UTC integration manifest
> 2171235 drm/i915/dp/mst: Add source port info to debugfs output
> b92ba82 drm/dp/mst: Enhance DP MST debugfs output
> c6df32b drm/edid: Add drm_edid_get_monitor_name()
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-04-15 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 17:18 [PATCH v4 1/3] drm/edid: Add drm_edid_get_monitor_name() Jim Bride
2016-04-14 17:18 ` [PATCH v4 2/3] drm/dp/mst: Enhance DP MST debugfs output Jim Bride
2016-04-14 17:18 ` [PATCH v4 3/3] drm/i915/dp/mst: Add source port info to " Jim Bride
2016-04-15 6:26 ` ✗ Fi.CI.BAT: failure for series starting with [v4,1/3] drm/edid: Add drm_edid_get_monitor_name() Patchwork
2016-04-15 12:37 ` Daniel Vetter [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=20160415123728.GV2510@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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