Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: failure for drm/i915: Expose more GPU properties through sysfs (rev6)
Date: Mon, 04 Dec 2017 18:48:34 -0000	[thread overview]
Message-ID: <20171204184834.17978.2717@emeril.freedesktop.org> (raw)
In-Reply-To: <20171204150238.28011-1-lionel.g.landwerlin@intel.com>

== Series Details ==

Series: drm/i915: Expose more GPU properties through sysfs (rev6)
URL   : https://patchwork.freedesktop.org/series/33950/
State : failure

== Summary ==

Test gem_eio:
        Subgroup in-flight-contexts:
                pass       -> DMESG-WARN (shard-snb) fdo#104058
Test kms_frontbuffer_tracking:
        Subgroup fbc-1p-primscrn-pri-indfb-draw-blt:
                pass       -> FAIL       (shard-snb)
        Subgroup fbc-1p-offscren-pri-shrfb-draw-render:
                pass       -> FAIL       (shard-snb) fdo#101623
Test drv_module_reload:
        Subgroup basic-reload-inject:
                pass       -> DMESG-WARN (shard-snb) fdo#102707 +2

fdo#104058 https://bugs.freedesktop.org/show_bug.cgi?id=104058
fdo#101623 https://bugs.freedesktop.org/show_bug.cgi?id=101623
fdo#102707 https://bugs.freedesktop.org/show_bug.cgi?id=102707

shard-hsw        total:2681 pass:1535 dwarn:2   dfail:0   fail:10  skip:1134 time:9503s
shard-snb        total:2681 pass:1305 dwarn:3   dfail:0   fail:14  skip:1359 time:8159s

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7397/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-12-04 18:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 15:02 [PATCH v6 0/5] drm/i915: Expose more GPU properties through sysfs Lionel Landwerlin
2017-12-04 15:02 ` [PATCH v6 1/5] drm: add card symlink in render sysfs directory Lionel Landwerlin
2017-12-04 15:02 ` [PATCH v6 2/5] drm/i915: store all subslice masks Lionel Landwerlin
2017-12-04 15:02 ` [PATCH v6 3/5] drm/i915/debugfs: reuse max slice/subslices already stored in sseu Lionel Landwerlin
2017-12-04 15:02 ` [PATCH v6 4/5] drm/i915: expose engine availability through sysfs Lionel Landwerlin
2017-12-04 15:02 ` [PATCH v6 5/5] drm/i915: expose EU topology " Lionel Landwerlin
2017-12-04 16:02 ` ✓ Fi.CI.BAT: success for drm/i915: Expose more GPU properties through sysfs (rev6) Patchwork
2017-12-04 18:48 ` Patchwork [this message]
2017-12-07  9:21 ` [Intel-gfx] [PATCH v6 0/5] drm/i915: Expose more GPU properties through sysfs Tvrtko Ursulin
2017-12-11 10:50   ` Joonas Lahtinen
2017-12-11 13:29     ` Lionel Landwerlin
2017-12-11 14:38     ` [Intel-gfx] " Tvrtko Ursulin
2017-12-11 14:47       ` Lionel Landwerlin
2017-12-11 21:05       ` [Intel-gfx] " Daniel Vetter
2017-12-12 11:19         ` Tvrtko Ursulin
2017-12-12 14:33           ` Lionel Landwerlin
2017-12-13  8:17             ` Daniel Vetter
2017-12-13 13:35               ` Chris Wilson
2017-12-13 15:09                 ` Lionel Landwerlin
2017-12-13 15:06               ` Lionel Landwerlin
2017-12-12 15:18           ` Daniel Vetter

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=20171204184834.17978.2717@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lionel.g.landwerlin@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