From: Patchwork <patchwork@emeril.freedesktop.org>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: warning for tests: Drop gem_bad_length as redundant
Date: Wed, 11 Oct 2017 01:24:50 -0000 [thread overview]
Message-ID: <20171011012450.1256.39465@emeril.freedesktop.org> (raw)
In-Reply-To: <20171010122856.10504-1-joonas.lahtinen@linux.intel.com>
== Series Details ==
Series: tests: Drop gem_bad_length as redundant
URL : https://patchwork.freedesktop.org/series/31655/
State : warning
== Summary ==
Test gem_eio:
Subgroup wait:
pass -> DMESG-WARN (shard-hsw) fdo#102886 +4
Test kms_universal_plane:
Subgroup cursor-fb-leak-pipe-A:
pass -> SKIP (shard-hsw)
Test kms_flip:
Subgroup modeset-vs-vblank-race:
pass -> FAIL (shard-hsw) fdo#102919
Test kms_plane:
Subgroup plane-position-hole-pipe-C-planes:
pass -> DMESG-WARN (shard-hsw)
fdo#102886 https://bugs.freedesktop.org/show_bug.cgi?id=102886
fdo#102919 https://bugs.freedesktop.org/show_bug.cgi?id=102919
shard-hsw total:2551 pass:1428 dwarn:5 dfail:0 fail:14 skip:1104 time:9567s
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_313/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:[~2017-10-11 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 12:28 [CI i-g-t] tests: Drop gem_bad_length as redundant Joonas Lahtinen
2017-10-10 18:23 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-10-11 1:24 ` Patchwork [this message]
2017-10-12 8:37 ` [CI i-g-t] " Joonas Lahtinen
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=20171011012450.1256.39465@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox