From: Patchwork <patchwork@emeril.freedesktop.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: warning for drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits
Date: Wed, 17 Jan 2018 14:30:49 -0000 [thread overview]
Message-ID: <20180117143049.14508.31777@emeril.freedesktop.org> (raw)
In-Reply-To: <20180117115108.29608-1-maarten.lankhorst@linux.intel.com>
== Series Details ==
Series: drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits
URL : https://patchwork.freedesktop.org/series/36608/
State : warning
== Summary ==
Test kms_frontbuffer_tracking:
Subgroup fbc-1p-primscrn-cur-indfb-draw-mmap-cpu:
pass -> SKIP (shard-snb)
Subgroup fbc-1p-offscren-pri-shrfb-draw-render:
fail -> PASS (shard-snb) fdo#101623
Subgroup fbc-1p-primscrn-pri-shrfb-draw-render:
pass -> INCOMPLETE (shard-hsw) fdo#103167
Test perf:
Subgroup polling:
pass -> FAIL (shard-hsw) fdo#102252
Test drv_suspend:
Subgroup fence-restore-untiled:
skip -> PASS (shard-snb) fdo#102365
Test kms_flip:
Subgroup flip-vs-modeset-vs-hang:
pass -> INCOMPLETE (shard-snb) fdo#103821
fdo#101623 https://bugs.freedesktop.org/show_bug.cgi?id=101623
fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
fdo#102252 https://bugs.freedesktop.org/show_bug.cgi?id=102252
fdo#102365 https://bugs.freedesktop.org/show_bug.cgi?id=102365
fdo#103821 https://bugs.freedesktop.org/show_bug.cgi?id=103821
shard-hsw total:2642 pass:1653 dwarn:1 dfail:0 fail:12 skip:974 time:13691s
shard-snb total:2737 pass:1309 dwarn:1 dfail:0 fail:11 skip:1415 time:7708s
Blacklisted hosts:
shard-apl total:2693 pass:1666 dwarn:1 dfail:0 fail:22 skip:1002 time:13047s
shard-kbl total:2753 pass:1819 dwarn:21 dfail:1 fail:22 skip:890 time:10703s
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7693/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-01-17 14:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 11:51 [PATCH] drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits Maarten Lankhorst
2018-01-17 12:12 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-01-17 14:30 ` Patchwork [this message]
2018-01-17 16:13 ` Patchwork
2018-01-17 18:29 ` [Intel-gfx] [PATCH] " Sean Paul
2018-01-17 18:29 ` Sean Paul
2018-01-17 18:39 ` [Intel-gfx] " Maarten Lankhorst
2018-01-17 20:18 ` Sean Paul
2018-01-29 15:41 ` Leo Li
2018-01-30 10:28 ` Maarten Lankhorst
2018-01-31 19:57 ` Harry Wentland
2018-01-31 19:57 ` Harry Wentland
2018-02-01 10:30 ` [Intel-gfx] " Maarten Lankhorst
2018-02-01 10:30 ` Maarten Lankhorst
2018-02-01 14:29 ` Harry Wentland
2018-01-25 11:14 ` ✗ Fi.CI.IGT: warning for " Patchwork
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=20180117143049.14508.31777@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.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.