From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: failure for tests/psr: Don't strcmp CRCs that are not NULL terminated. (rev2)
Date: Wed, 20 Sep 2017 04:12:26 -0000 [thread overview]
Message-ID: <20170920041226.23784.815@emeril.freedesktop.org> (raw)
In-Reply-To: <20170919015509.10736-1-dhinakaran.pandiyan@gmail.com>
== Series Details ==
Series: tests/psr: Don't strcmp CRCs that are not NULL terminated. (rev2)
URL : https://patchwork.freedesktop.org/series/30564/
State : failure
== Summary ==
Test gem_eio:
Subgroup in-flight-external:
dmesg-warn -> PASS (shard-hsw)
Subgroup in-flight-contexts:
dmesg-warn -> PASS (shard-hsw)
Test kms_setmode:
Subgroup basic:
fail -> PASS (shard-hsw) fdo#99912
Test kms_frontbuffer_tracking:
Subgroup fbc-1p-primscrn-shrfb-pgflip-blt:
pass -> FAIL (shard-hsw)
Test kms_busy:
Subgroup extended-modeset-hang-newfb-with-reset-render-C:
pass -> DMESG-WARN (shard-hsw) fdo#102249
fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
fdo#102249 https://bugs.freedesktop.org/show_bug.cgi?id=102249
shard-hsw total:2271 pass:1217 dwarn:2 dfail:0 fail:14 skip:1038 time:9615s
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_231/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-09-20 4:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 1:55 [PATCH i-g-t] tests/psr: Don't strcmp CRCs that are not NULL terminated Dhinakaran Pandiyan
2017-09-19 10:19 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-09-19 22:47 ` [PATCH i-g-t v2] " Dhinakaran Pandiyan
2017-09-22 1:01 ` Sripada, Radhakrishna
2017-09-20 0:36 ` ✓ Fi.CI.BAT: success for tests/psr: Don't strcmp CRCs that are not NULL terminated. (rev2) Patchwork
2017-09-20 4:12 ` 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=20170920041226.23784.815@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=dhinakaran.pandiyan@intel.com \
--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.