From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.BAT: failure for drm/atomic: Make drm_framebuffer_remove atomic, again.
Date: Wed, 22 Feb 2017 12:48:11 +0100 [thread overview]
Message-ID: <975ad6c4-2b18-fc47-fc60-f9b9f95299db@linux.intel.com> (raw)
In-Reply-To: <20170221152344.24239.80784@emeril.freedesktop.org>
Op 21-02-17 om 16:23 schreef Patchwork:
> == Series Details ==
>
> Series: drm/atomic: Make drm_framebuffer_remove atomic, again.
> URL : https://patchwork.freedesktop.org/series/20008/
> State : failure
>
> == Summary ==
>
> Series 20008v1 drm/atomic: Make drm_framebuffer_remove atomic, again.
> https://patchwork.freedesktop.org/api/1.0/series/20008/revisions/1/mbox/
>
> Test gem_exec_basic:
> Subgroup gtt-render:
> incomplete -> PASS (fi-byt-j1900)
> Test kms_pipe_crc_basic:
> Subgroup nonblocking-crc-pipe-a-frame-sequence:
> pass -> DMESG-FAIL (fi-snb-2520m)
> Subgroup nonblocking-crc-pipe-b:
> pass -> DMESG-FAIL (fi-snb-2520m)
> Subgroup nonblocking-crc-pipe-b-frame-sequence:
> pass -> DMESG-FAIL (fi-snb-2520m)
> Subgroup read-crc-pipe-a:
> pass -> DMESG-FAIL (fi-snb-2520m)
> Subgroup read-crc-pipe-a-frame-sequence:
> pass -> INCOMPLETE (fi-snb-2520m)
Sigh, last patch regresses on the crc tests again. snb-2600 is fine so something specific to the configuration there..
https://patchwork.freedesktop.org/series/20012/ are the ci results for this series without the last patch, so
please apply patch 1 and 2 only?
~Maarten
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-02-22 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 13:51 [PATCH 0/3] drm/atomic: Make drm_framebuffer_remove atomic, again Maarten Lankhorst
[not found] ` <1487685102-31991-1-git-send-email-maarten.lankhorst-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-02-21 13:51 ` [PATCH 1/3] drm/atomic: Make disable_all helper fully disable the crtc Maarten Lankhorst
2017-02-23 15:03 ` Sean Paul
2017-02-23 20:10 ` Maarten Lankhorst
2017-02-21 13:51 ` [PATCH 2/3] drm: Convert drm_framebuffer_remove to atomic, v4 Maarten Lankhorst
2017-02-23 15:09 ` Sean Paul
2017-02-28 12:03 ` Daniel Vetter
2017-02-21 13:51 ` [PATCH 3/3] drm/atomic: Try to preserve the crtc enabled state in drm_atomic_remove_fb Maarten Lankhorst
2017-02-23 15:24 ` Sean Paul
2017-02-27 12:01 ` Maarten Lankhorst
2017-02-21 15:23 ` ✗ Fi.CI.BAT: failure for drm/atomic: Make drm_framebuffer_remove atomic, again Patchwork
2017-02-22 11:48 ` Maarten Lankhorst [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=975ad6c4-2b18-fc47-fc60-f9b9f95299db@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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 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.