From: Patchwork <patchwork@emeril.freedesktop.org>
To: Navare@emeril.freedesktop.org, Manasi D <manasi.d.navare@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm: Add DPCD definitions for DP 1.4 DSC feature (rev4)
Date: Wed, 15 Mar 2017 08:32:57 -0000 [thread overview]
Message-ID: <20170315083257.9829.76570@emeril.freedesktop.org> (raw)
In-Reply-To: <1489521689-1162-1-git-send-email-manasi.d.navare@intel.com>
== Series Details ==
Series: drm: Add DPCD definitions for DP 1.4 DSC feature (rev4)
URL : https://patchwork.freedesktop.org/series/19666/
State : failure
== Summary ==
Series 19666v4 drm: Add DPCD definitions for DP 1.4 DSC feature
https://patchwork.freedesktop.org/api/1.0/series/19666/revisions/4/mbox/
Test gem_exec_flush:
Subgroup basic-batch-kernel-default-wb:
pass -> INCOMPLETE (fi-skl-6770hq)
Subgroup basic-uc-pro-default:
pass -> INCOMPLETE (fi-skl-6700hq) fdo#100130
Subgroup basic-uc-ro-default:
pass -> INCOMPLETE (fi-skl-6260u)
Test kms_cursor_legacy:
Subgroup basic-busy-flip-before-cursor-atomic:
fail -> PASS (fi-snb-2520m)
fdo#100130 https://bugs.freedesktop.org/show_bug.cgi?id=100130
fi-bdw-5557u total:278 pass:267 dwarn:0 dfail:0 fail:0 skip:11 time: 455s
fi-bsw-n3050 total:278 pass:239 dwarn:0 dfail:0 fail:0 skip:39 time: 579s
fi-bxt-j4205 total:278 pass:259 dwarn:0 dfail:0 fail:0 skip:19 time: 543s
fi-bxt-t5700 total:278 pass:258 dwarn:0 dfail:0 fail:0 skip:20 time: 558s
fi-byt-j1900 total:278 pass:251 dwarn:0 dfail:0 fail:0 skip:27 time: 500s
fi-byt-n2820 total:278 pass:247 dwarn:0 dfail:0 fail:0 skip:31 time: 502s
fi-ilk-650 total:278 pass:228 dwarn:0 dfail:0 fail:0 skip:50 time: 448s
fi-ivb-3770 total:278 pass:260 dwarn:0 dfail:0 fail:0 skip:18 time: 497s
fi-skl-6260u total:55 pass:53 dwarn:0 dfail:0 fail:0 skip:1 time: 0s
fi-skl-6700hq total:53 pass:45 dwarn:0 dfail:0 fail:0 skip:7 time: 0s
fi-skl-6770hq total:52 pass:50 dwarn:0 dfail:0 fail:0 skip:1 time: 0s
fi-snb-2520m total:278 pass:250 dwarn:0 dfail:0 fail:0 skip:28 time: 551s
fi-snb-2600 total:278 pass:249 dwarn:0 dfail:0 fail:0 skip:29 time: 418s
c641417b70c6b78efca29ae732d7cbf5716ac6d5 drm-tip: 2017y-03m-14d-16h-04m-56s UTC integration manifest
88ee5288 drm: Add DPCD definitions for DP 1.4 DSC feature
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_4171/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-15 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 20:01 [PATCH v3] drm: Add DPCD definitions for DP 1.4 DSC feature Manasi Navare
2017-03-15 8:32 ` Patchwork [this message]
2017-03-15 8:46 ` ✗ Fi.CI.BAT: failure for drm: Add DPCD definitions for DP 1.4 DSC feature (rev4) Patchwork
2017-03-15 8:49 ` ✓ Fi.CI.BAT: success " Patchwork
2017-03-16 13:47 ` [PATCH v3] drm: Add DPCD definitions for DP 1.4 DSC feature Ander Conselvan De Oliveira
2017-04-03 22:35 ` Manasi Navare
2017-04-03 22:51 ` [PATCH v4] " Manasi Navare
2017-04-06 21:37 ` Manasi Navare
2017-04-20 14:47 ` Jani Nikula
2017-04-03 23:04 ` ✓ Fi.CI.BAT: success for drm: Add DPCD definitions for DP 1.4 DSC feature (rev5) 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=20170315083257.9829.76570@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=Navare@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=manasi.d.navare@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.