From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Srinivas, Vidya" <vidya.srinivas@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: warning for Add support for NV12
Date: Wed, 11 Oct 2017 01:21:40 -0000 [thread overview]
Message-ID: <20171011012140.1256.95002@emeril.freedesktop.org> (raw)
In-Reply-To: <1507637715-17122-1-git-send-email-vidya.srinivas@intel.com>
== Series Details ==
Series: Add support for NV12
URL : https://patchwork.freedesktop.org/series/31648/
State : warning
== Summary ==
Test gem_eio:
Subgroup wait:
pass -> DMESG-WARN (shard-hsw) fdo#102886 +3
Test drv_module_reload:
Subgroup basic-reload-inject:
pass -> DMESG-WARN (shard-hsw) fdo#102707
Test kms_cursor_legacy:
Subgroup flip-vs-cursor-busy-crc-atomic:
pass -> DMESG-WARN (shard-hsw)
fdo#102886 https://bugs.freedesktop.org/show_bug.cgi?id=102886
fdo#102707 https://bugs.freedesktop.org/show_bug.cgi?id=102707
shard-hsw total:2602 pass:1429 dwarn:7 dfail:0 fail:63 skip:1103 time:9614s
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_312/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-10-11 1:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 12:15 [PATCH i-g-t 0/2] Add support for NV12 Vidya Srinivas
2017-10-10 12:15 ` [PATCH i-g-t 1/2] Prep work for adding NV12 testcase Vidya Srinivas
2017-10-10 12:15 ` [PATCH i-g-t 2/2] tests/test_nv12.c: Add test to cover NV12 format testing Vidya Srinivas
2017-10-10 12:21 ` Daniel Vetter
2017-10-12 7:19 ` Srinivas, Vidya
2017-10-12 11:13 ` Daniel Vetter
2017-10-13 2:47 ` Srinivas, Vidya
2017-10-10 18:04 ` ✓ Fi.CI.BAT: success for Add support for NV12 Patchwork
2017-10-11 1:21 ` Patchwork [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=20171011012140.1256.95002@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vidya.srinivas@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.